Skip to main content
Glama

MedaRep

Save a custom territory

save_territory
DestructiveIdempotent

Save a territory on the rep's MedaRep account from a metro, county FIPS codes and/or ZIP codes, optionally with its procedure family; it then shows under /territories and in my_territories. Saving under an existing territory's name replaces it. The plan limits how many territories are kept. Use only when the user asks to save one.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe territory's name, e.g. "South Charlotte knee".
zipsNo5-digit ZIP codes forming a custom territory (as my_territories returns them).
metroNoMetro area by name ("Charlotte") or 5-digit CBSA code (16740). Can cross state lines.
familyNoProcedure family key from coverage (e.g. knee-arthroplasty, lumbar-fusion) or a plain name.
countiesNo5-digit county FIPS codes forming a custom territory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: saving under an existing name replaces it, and the plan caps how many territories are kept. The replace semantics are consistent with destructiveHint=true and idempotentHint=true, so nothing contradicts. However, it does not say whether replacement prompts or is silent, nor what happens to accounts already assigned to the overwritten territory.

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

Conciseness4/5

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

Front-loaded with the action and inputs, then behavior, then the usage guardrail. Dense but each sentence carries information; the '/territories and in my_territories' phrasing is slightly redundant but serves as a discoverability cue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation with no output schema, the description covers inputs, replacement semantics, quota limits, and the when-to-save guardrail across four sentences. The only unstated item is response shape, which is not needed since no output schema exists and the effect is described as appearing in my_territories.

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?

Schema coverage is already 100%, but the description adds meaning the schema does not: that metro, counties, and zips are alternative/interchangeable territory sources rather than cumulative filters, and that family is optional. That compositional logic is exactly the information an agent needs and cannot get from the field descriptions alone.

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?

Specific verb and resource ('Save a territory ... from a metro, county FIPS codes and/or ZIP codes, optionally with its procedure family') that spells out the composition inputs, plus a note on where the result surfaces ('under /territories and in my_territories'). An agent can tell this is the write-side counterpart to the territory-reading tools without consulting the schema.

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?

Gives an explicit gating condition: 'Use only when the user asks to save one,' which prevents an agent from proactively persisting territories during exploratory analysis. It stops short of naming what to do instead (e.g. ranking or previewing a territory first), so no alternative is routed to.

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