Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_city

Delete a city record by its ID from the geopolitical catalog. Use this to remove outdated or incorrect city entries via the Statesman MCP Server.

Instructions

Delete a city record.

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

Input Schema

NameRequiredDescriptionDefault
idYesCity ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it only implies mutation. It does not state that the deletion is permanent/irreversible, whether related data is affected, what permissions are required, or how a missing or already-deleted ID is handled.

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?

One short sentence with zero padding and the core action front-loaded; there is no redundancy or awkward structure. Its brevity reflects under-specification rather than excess, so it is not penalized further here.

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

Completeness2/5

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

For a destructive single-parameter tool with no annotations and no output schema, the description should at minimum state irreversibility and the expected outcome. It omits both, leaving the agent unable to judge the consequences of invoking it.

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 description coverage is 100% for the single `id` parameter, including type and a positive-exclusive bound, so the schema already explains the input. The description adds nothing about the ID's origin (e.g., from `list_cities` or `get_city`), keeping this at the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names a verb and a resource ("Delete a city record"), so an agent knows the operation targets a city. However, it is essentially a restatement of the tool name `delete_city` and offers no differentiation from siblings such as `delete_country` or `delete_continent`, whose names alone imply the same pattern.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Nothing tells the agent whether related records must be removed first or which sibling to prefer 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.

Deploy Server

Other Tools