Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

upsert_continents_batch

Insert or update multiple continents in one call, matching existing records case-insensitively by name to avoid duplicates.

Instructions

Batch insert or update continents matching case-insensitively on name.

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

Input Schema

NameRequiredDescriptionDefault
continentsYesArray of continents to upsert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the non-obvious matching rule: case-insensitive on name, which determines create-vs-update behavior. It omits what happens to an existing record's description field, whether the batch is atomic on partial failure, and what the call returns (no output schema exists).

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?

A single front-loaded sentence with zero filler; the match-key rule is packed into the clause where it matters most.

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

Completeness3/5

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

For a batch write tool with no annotations and no output schema, the definition covers the essential matching semantics but leaves return values and partial-failure behavior undocumented. An agent knows what the tool does but not what it gets back or how errors surface.

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 100% with a single nested parameter, so the baseline is already 3, and the description adds meaning the schema does not: 'name' is the case-insensitive match key for upsert. It says nothing about the optional description field's overwrite behavior.

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 verb pair ('batch insert or update') plus the resource ('continents'), and 'batch' implicitly separates it from the single-record create_continent sibling. It stops short of naming the sibling alternatives outright, so the differentiation is inferred rather than stated.

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?

Batch upsert semantics imply 'use this when you have multiple continents and don't know which already exist,' which is a reasonable usage signal. However, it never states when to prefer create_continent or populate_continents, nor any prerequisite or exclusion.

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