Skip to main content
Glama

MedaRep

My saved territories

my_territories
Read-onlyIdempotent

The territories the rep drew and saved on MedaRep, each with a place (metro, counties, zips) to pass to rank_territory, incumbents, switching and the other territory tools, and its family when one was saved.

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": "my_territories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description earns credit for adding return-content context that annotations cannot supply — that each entry carries a place (metro, counties, zips) and a family when one was saved — which is useful given there is no output schema.

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

Conciseness3/5

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

It is a single sentence, but an overloaded one: 'and its family when one was saved' trails awkwardly and the clause about downstream tools is embedded mid-sentence. The subject (saved territories) is front-loaded, but the sentence would read better split into purpose and contents.

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 zero-parameter, read-only listing tool with no output schema, the description covers what is returned (place components, family association) and what the data feeds into. Minor gaps remain — ordering, whether incumbents are embedded or must be fetched separately — but nothing essential to calling it is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the mention of 'place' and 'family' clarifies field contents, not inputs.

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 names a specific resource — the territories a rep drew and saved on MedaRep — and implies retrieval rather than mutation, which separates it from save_territory. It also enumerates the payload (a place of metro/counties/zips plus a family), so an agent knows what it gets. It stops short of an explicit verb like 'list' or 'retrieve'.

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?

Usage is implied rather than stated: the place value is described as 'to pass to rank_territory, incumbents, switching and the other territory tools', which tells the agent what to do downstream but not explicitly when to call this tool instead of another. There are no exclusions or preconditions given.

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.

Resources