Skip to main content
Glama

DaedalMap Hurricane and Tropical Cyclone Data

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
Behavior4/5

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

Annotations declare readOnlyHint=true, so safety is known. The description augments this by detailing the return payload and the interaction contract. It doesn't describe failure behavior on invalid tool_name, but that's not critical for a read-only help tool.

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 sentences, front-loaded with purpose, packed with useful detail without padding. Every sentence earns its place.

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 one-parameter read-only helper, the description tells what to expect in the response and how to use it. It lists the response contents, so no output schema is needed.

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 covers tool_name 100% with a clear description ('Exact tool name from tools/list'). The description adds usage context (call before unfamiliar tool) but no additional syntax requirements, so baseline 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 states the tool returns guidance for any visible tool, listing specific content types (when to use, refusals, example, limits, outputs, provenance, next calls, interaction contract). This distinguishes it from sibling data tools (get_catalog, search_disaster_links) as a meta-help tool.

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

Usage Guidelines5/5

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

Explicitly instructs to call tools/list first, then call this before unfamiliar tool. This gives a clear when-to-use policy and a workflow. Sibling tools are for data, so no confusion about alternatives.

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

All DaedalMap Hurricane and Tropical Cyclone Data 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.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: catalog lists packs, get_pack returns pack metadata, get_tool_help explains tool usage, query_dataset executes data queries, and search_disaster_links discovers cross-disaster relationships. There is no meaningful overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern: get_catalog, get_pack, get_tool_help, query_dataset, search_disaster_links. The verb differences reflect different action types, but the structural pattern is uniform.

Tool Count5/5

Five tools is well-scoped for a data-access MCP server. The set covers discovery, metadata retrieval, tool guidance, querying, and relationship search without unnecessary bulk or redundancy.

Completeness4/5

The tool surface covers the full discovery-to-query workflow: find packs, inspect pack metadata, get tool help, query datasets, and search disaster link families. A minor gap is the lack of dataset-level schema or status tools, but these are partly covered by get_pack metadata and are not critical for the server's read-oriented purpose.

Resources