Skip to main content
Glama

DaedalMap Administrative Boundaries (loc_id to polygon)

by com.daedalmap

Get Tool Help

get_tool_help
Read-only

Free blind-caller guidance for one tool visible on this MCP facade. Returns when to use it, what it refuses, a working example, effective access limits, important outputs, provenance fields, recommended next calls, and the shared natural-language-to-strict-JSON interaction contract. Use tools/list to discover names, then call this before an unfamiliar tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_nameYesExact tool name from tools/list.

TDQS

A4.5/5.0
Behavior5/5

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

The description extensively discloses behavioral traits beyond the readOnlyHint annotation, including 'what it refuses', 'effective access limits', 'provenance fields', and the 'natural-language-to-strict-JSON interaction contract'. This provides substantial insight into the tool's behavior and outputs.

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?

The description is compact—two sentences—with the primary purpose front-loaded. The list of returned content is informative and each clause earns its place without redundancy.

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?

Given the single parameter, no output schema, and readOnly annotation, the description provides a thorough overview of what the tool does, what it returns, and the recommended workflow, making it self-sufficient for an unfamiliar caller.

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?

The input schema fully describes 'tool_name' as 'Exact tool name from tools/list', and the description reinforces this by saying 'Use tools/list to discover names'. With 100% schema coverage, the description adds minimal new semantic value for the parameter, so the baseline score of 3 is appropriate.

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?

The description clearly identifies the tool as a help/metadata provider for a single tool, listing specific returned content categories (when to use, refusals, example, access limits, outputs, provenance, next calls, contract). It contrasts with the sibling geometry tools by being a meta-guidance resource.

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?

The description gives explicit usage context: 'Use tools/list to discover names, then call this before an unfamiliar tool.' This establishes a clear workflow and when to invoke it. It does not explicitly mention exclusions or alternatives, but the purpose is unambiguous.

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

All DaedalMap Administrative Boundaries (loc_id to polygon) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: discovery (get_catalog, get_pack), geometry retrieval (get_geometry), hierarchy (loc_id_info, resolve_loc_id_scope), relationship analysis (compare_geographies), preflight (check_geometry), export estimation and creation (estimate_geometry_package, create_geometry_export), job status (get_job_status), and help (get_tool_help). Even closely related tools like check_geometry and estimate_geometry_package address different concerns (shape availability vs export artifact), leaving no ambiguity.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (check_geometry, compare_geographies, create_geometry_export, estimate_geometry_package, get_catalog, get_geometry, get_job_status, get_pack, get_tool_help, resolve_loc_id_scope). However, 'loc_id_info' breaks the pattern by being a noun phrase rather than a verb action, causing a minor deviation from the otherwise uniform convention.

Tool Count5/5

With 11 tools, the server covers the key operations for administrative boundary data—discovery, geometry retrieval, hierarchy navigation, comparison, export, and job management—without overreach. Each tool is necessary for a coherent workflow, and the count fits well within the typical 3-15 range for a domain-specific MCP server.

Completeness5/5

The tool set effectively covers the full lifecycle needed for administrative boundary use: discovery (catalog/pack), preflight checks, geometry retrieval, hierarchical navigation, relationship analysis, export estimation/creation, and job status. It includes essential utilities like get_tool_help for onboarding. No obvious gaps exist for the server's purpose; if anything, it is notably thorough for read/export operations.

Resources