Skip to main content
Glama

groundtruth

ha_long_disruptions

Read-only

Recorded Ha Long / Quang Ninh sailing suspensions (storm-related) with authority, document number and source. Filter by province or by a date.

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": "ha_long_disruptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
provinceNo
active_onNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful provenance context — that these are official records tied to a naming authority, document number and source, and that the scope is storm-related only — but says nothing about coverage periods or how complete the record set is, which matters for a curated list returned without an output schema.

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?

Two sentences, front-loaded with the resource and scope, then the filtering options. No filler, though the parenthetical '(storm-related)' and the field list could be tightened.

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 two-optional-parameter read tool with no output schema, the description does the heavy lifting by naming the fields returned (authority, document number, source) and the event scope. The remaining gap is coverage range — an agent cannot tell how far back the records go.

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 coverage is 50%: active_on documents its YYYY-MM-DD format, province is bare. The description clarifies that province is a province filter and that the date filter is an alternative ('or'), implying the two filters can be used independently, which the schema does not say. That is real added meaning, but it stops short of explaining what date is matched against (start, end, or any overlap).

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 resource — recorded Ha Long / Quang Ninh sailing suspensions — and scopes it to storm-related events, with the record fields it carries (authority, document number, source). The retrieval verb is only implicit ('Recorded'), but the resource is unambiguous and unrelated to any sibling.

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 statement of when to use this tool, when not to, or what alternative to prefer. The only hint at usage is 'Filter by province or by a date', which describes how to narrow results but not when the tool is the right choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources