Skip to main content
Glama

get_legislator

Read-only

Retrieve a Utah legislator by ID or partial name; ambiguous names return candidate matches.

Instructions

Get one legislator by id or name. Returns candidates if the name is ambiguous.

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": {
      "who": "<who>"
    },
    "name": "get_legislator"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoYesLegislator id (e.g. 'PETERT') or part of a name.
detailNobrief = one line per item; standard adds summaries; full adds everything.standard
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: ambiguous names return candidates rather than failing, though it does not say whether that is an error, a list, or how many candidates come back.

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 short sentences with zero padding; the primary action is stated first and the ambiguity caveat follows immediately.

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 three-parameter read tool with full schema coverage and read-only annotations, the definition covers the essentials. The one gap is what the ambiguous-name response looks like and how the agent should proceed, which matters for a name-based lookup.

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 100%, so 'who', 'detail', and 'max_chars' are already documented with examples and an enum. The description only restates that 'who' accepts an id or a name, adding little beyond the schema's own 'Legislator id (e.g. PETERT) or part of a name'.

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?

The description opens with a specific verb and resource ('Get one legislator') and constrains the lookup to 'by id or name', which implicitly separates it from the bulk list_legislators sibling. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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?

The ambiguity clause implies you can pass a partial name and will be handed back candidates, which hints at how to use the tool, but there is no explicit when-to-use/when-not guidance and no pointer to list_legislators for enumeration or to a lookup alternative for other entity types.

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