get_firm
Get one firm's public directory record by slug. Returns null for unknown or non-public (suppressed) firms.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | firm slug, e.g. "a-lign" |
directory
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden and discloses the key behavioral detail that unknown or suppressed firms return null. Additional context like auth requirements would improve it.
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?
Single sentence concisely states the purpose and behavioral note, with no extraneous information.
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?
Given the tool's simplicity, the description covers purpose, edge case behavior, and key constraint, though output structure is not mentioned (no output schema provided).
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 covers 100% of the single parameter with a description and example. The tool description adds no extra parameter semantics beyond reinforcing the slug-based lookup.
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?
The description clearly states the tool retrieves a single firm's public directory record by slug, distinguishing it from sibling tools like search_firms that handle multiple results.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus siblings like search_firms, but the description implies it is for retrieving a specific firm by slug.
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.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: get_firm retrieves a specific firm, get_introduction_path provides instructions for introductions, get_resource fetches a single resource, list_resources lists resources, and search_firms searches firms. No overlap.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (get_firm, get_introduction_path, get_resource, list_resources, search_firms). No deviations.
Tool Count5/5
Five tools is appropriate for a read-only directory server. Each tool covers a distinct operation, and the count is not excessive or insufficient.
Completeness4/5
The tool surface covers firm lookup/search, resource listing/retrieval, and introduction guidance. Missing a simple list all firms tool (only search is available), but this is a minor gap for a read-only directory.