Tools

Efimis tools describe their purpose and inputs so your AI assistant can discover them after connecting. Follow the connection guide to sign in using Claude, Codex or ChatGPT.

Tool availability

• Tool availability is filtered by user permissions; direct calls to unavailable tools are rejected.
• Administrators may see the full tool set, subject to enabled tenant features.
• Some tool families are enabled per firm.
• Descriptions are localized to the firm’s region.

Build the agent’s available tools from tools/list. Do not hard-code the list or reuse one user’s list for another user or firm.

Give the agent useful context

Provide today’s date and timezone, the firm’s financial-period boundaries, the user’s identity, region, currency and preferred date formats. This helps resolve questions such as “my matters”, “last quarter” and “this financial year”. Keep these values in a prompt template populated for each conversation.

Define the agent’s scope, guidance for choosing overlapping tools, and output conventions. Allow chained tool calls so the agent can resolve a matter before querying or acting on it. Use structured outcomes to distinguish answered questions, in-scope requests that could not be completed, and out-of-scope requests.

Manage conversation state

Persist conversation history in your application. An MCP transport session is not the user’s conversation history. Summarize long histories while preserving matters, people and date ranges referenced by follow-up questions.

Support cancellation and guard against duplicate submissions. A connection failure does not prove that an operation failed: check the outcome before retrying a write.

Present the actual results

Route tabular tool results to a grid or pivot where possible, with prose explaining the findings. Resolve document identifiers returned by billing tools and surface usable files. A formatting pass can apply regional conventions, provided it preserves amounts, identifiers and meaning.

Handle write actions deliberately

Confirm the target and material details before posting work items, cost recoveries or requisitions, or drafting invoices. Resolve the matter or entity with a read tool first. Show what was created and its identifier, and use the product’s review step where available.

Test with administrators and ordinary users, and across supported regions. Repeat identity and tool checks after switching accounts or firms.