get_settlementReturn the complete stored record and official source links for one settlement ID produced by a search.
| Name | Required | Description | Default |
|---|---|---|---|
| settlement_id | Yes | Exact settlement identifier returned by a search. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by stating the returned data is the 'complete stored record' and includes 'official source links,' which goes beyond 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence communicates the core action, scope, and output without wasted words. Every phrase contributes meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a low-complexity single-parameter retrieval, the description, rich annotations, and output schema cover everything needed for an agent to select and call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the only parameter settlement_id is already described as the 'Exact settlement identifier returned by a search.' The description reinforces this but adds no significant new meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Return the complete stored record and official source links for one settlement ID produced by a search.' It clearly distinguishes this tool from siblings like search_settlements and get_settlements by focusing on retrieving a single, already-known settlement record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly implies usage after a search has produced a settlement ID, saying 'one settlement ID produced by a search.' However, it does not explicitly state when not to use it or name alternatives, so it misses the highest tier of guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: dataset metadata, single-record retrieval, batch retrieval, single search, and batch search. No overlapping boundaries or potential for misselection.
All tool names follow a consistent verb_noun snake_case pattern (get_dataset_info, get_settlement, get_settlements, search_settlements, search_settlements_batch). Verbs and noun plurality are used logically and consistently.
With exactly 5 tools, the server is well-scoped for its apparent purpose of settlement searching and retrieval. Each tool fills a necessary role without redundancy, making the count ideal.
The tool surface fully covers the read-only workflow: dataset-level info, targeted retrieval (single and batch), and search (single and batch). No obvious gaps for the domain, as update/create/delete operations are not implied by the server's purpose.