Skip to main content
Glama
Sign In

apibase

by io.github.whiteknightonhorse
OverviewDiscussionsAdmin

List Argentine Provinces

indec-georef.admin.provinces
Read-onlyIdempotent

List or search Argentina's 24 provinces (incl. Ciudad Autónoma de Buenos Aires) by name. Returns id, name, and centroid coordinates for each. Data: apis.datos.gob.ar/georef (INDEC), no auth required.

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": "indec-georef.admin.provinces"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum number of provinces to return (1-50, default 10).
queryNoFilter provinces by name substring, case-insensitive (e.g. "buenos" for Buenos Aires). Omit to list all 24 provinces (incl. CABA).

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context about the data source (INDEC georef) and no-auth requirement. It does not disclose rate limits or pagination details, but that is minor given the schema covers max.

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?

Two efficient sentences with the action front-loaded, plus essential provenance and auth info. No filler or repetition.

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 simple read-only list/search tool with full schema and output schema, the description is nearly complete. It includes data source, auth state, and return fields. The only gap is lack of sibling differentiation, but the tool name resolves ambiguity.

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% with clear parameter descriptions, including default for max and substring semantics for query. The description only adds 'by name', which is redundant with the schema. Baseline 3 is appropriate.

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 states a specific verb (list/search), a precise resource (Argentina's 24 provinces), and includes a clarifying detail (CABA). It does not explicitly distinguish from sibling georef tools like departments or localities, but the tool name itself disambiguates.

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 explicit when-to-use guidance or mention of alternatives. The description notes 'no auth required' which is a prerequisite but does not say 'use this for provinces, use departments for departments' or when query vs list is preferable. An agent must infer from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apibase toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources