Skip to main content
Glama

get_accountant

Read-only

Get the full published profile of one accountant by the slug returned by list_accountants, including biography, public contact details, certifications, verification and firm Q&A when published.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_accountant"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a read-only, closed-world operation. The description adds one genuine behavioral trait beyond them: the result is a published profile, with sections such as firm Q&A appearing only 'when published', which warns the agent that fields may be absent. It says nothing about not-found handling, partial records, or response size, so the addition is real but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence stating the action, the scope, the identifier source, and the payload contents. The trailing field list is dense but every item informs the caller what to expect; only the 'including...' tail could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe return contents, and it does so by enumerating the profile sections and flagging conditional publication. The remaining gap is error behavior for an unknown or malformed slug, which is minor for a simple single-record getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only supplies a pattern and maxLength for 'slug', so the description must carry the meaning. It does by identifying the slug as the identifier produced by list_accountants, which is the missing semantic link; format constraints are already handled by the schema pattern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Get the full published profile of one accountant') and enumerates what the profile contains: biography, contact details, certifications, verification, firm Q&A. It also distinguishes itself from the list-style sibling by anchoring the single-record scope to the slug returned by list_accountants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by the slug returned by list_accountants' gives an explicit prerequisite workflow: list first, then fetch one record. It does not state exclusions (e.g., that it is not a search endpoint or what to do when the slug is unknown), so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources