Skip to main content
Glama

Agent Index — GRC & Compliance

Get an audit-firm listing

get_auditor
Read-onlyIdempotent

Use when the user names a specific audit firm and wants its listing details. Returns that firm, including listing tier, the Verified flag, offices, frameworks and accreditation registry URLs.

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_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAuditor slug, e.g. schellman

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value by disclosing the return payload (listing tier, Verified flag, offices, frameworks, accreditation registry URLs), which matters because no output schema exists. It does not say what happens for an unknown or ambiguous slug.

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

Conciseness5/5

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

Two sentences, front-loaded with the usage condition followed by the return shape. Nothing is redundant or padded.

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?

For a one-parameter read tool with rich annotations, the definition covers when to call it and what comes back. The only meaningful gap is failure behavior on an unknown slug, which an agent would want before calling.

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

Parameters3/5

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

There is a single parameter at 100% schema description coverage, and the schema already supplies both the format hint and the example ('schellman'). The description adds no extra meaning about slug casing, aliasing, or lookup behavior, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource (retrieve one audit firm's listing) and enumerates the returned fields, so an agent can tell it apart from a search-style tool. It does not name the sibling search_auditors explicitly, leaving the single-vs-multi distinction to be inferred from the word 'specific'.

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?

'Use when the user names a specific audit firm and wants its listing details' gives a clear triggering condition. There is no explicit when-not or named alternative (e.g. 'use search_auditors when you only have a partial name'), so the routing guidance stops short of full coverage.

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.