Skip to main content
Glama

Agent Index — GRC & Compliance

Search compliance audit firms

search_auditors
Read-onlyIdempotent

Use when the user asks which firms can audit or certify them (SOC 2, ISO 27001, ISO 42001, PCI DSS, HITRUST, FedRAMP, CMMC C3PAO), by country or US state, or whether a firm is accredited. Returns Verified and registry-listed firms, labelled by listing tier. Not a ranking or endorsement.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_auditors"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoDated snapshot id: soc2-audit-firms, anab-iso-27001, or fedramp-3pao-soc2. Returns that list. Each row uses the same verified flag as other registry snapshots (false when the row is not a Verified listing). Not a ranking.
limitNo
queryNoFree-text query over firm name, headquarters, frameworks and accreditation bodies
countryNoHeadquarters or office country (US, United Kingdom, India, …)
frameworkNoFramework tag, e.g. SOC 2, ISO 27001, PCI DSS, CERT-In
accreditation_bodyNoAccreditation body, e.g. ANAB, UKAS, PCI SSC QSA, CERT-In

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / list
      Added value: +{
      +  "description": "Dated snapshot id: soc2-audit-firms, anab-iso-27001, or fedramp-3pao-soc2. Returns that list. Each row uses the same verified flag as other registry snapshots (false when the row is not a Verified listing). Not a ranking.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real context: results include both Verified and registry-listed firms labelled by listing tier, and it explicitly disclaims ranking/endorsement, which pre-empts a likely agent misinterpretation. Pagination/limit behavior is left to the schema.

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: the trigger and scope come first, the return semantics second, with the non-endorsement caveat last. No filler and no restatement of the tool name.

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?

All six parameters are optional, there is no output schema, and annotations carry the safety profile, so the description only needs to convey trigger and result semantics — which it does. Minor gaps are the absence of pagination/limit guidance and no pointer to the single-firm detail tool.

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?

Schema coverage is 83%, so the schema already documents the list, query, country, framework and accreditation_body parameters. The description only indirectly reinforces the country/state and framework dimensions and adds no syntax, format, or matching-behavior detail beyond the schema. Baseline 3 applies.

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 (search for compliance audit/certification firms) and enumerates the frameworks covered, plus the country/state and accreditation dimensions. The closing 'Not a ranking or endorsement' distinguishes it from ranking-oriented siblings like compare_agents and get_alternatives.

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?

Opens with an explicit trigger: 'Use when the user asks which firms can audit or certify them... or whether a firm is accredited.' That is clear when-to-use guidance, but it does not name an alternative for drilling into a single firm (e.g. get_auditor) or state when-not to use it.

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.