Skip to main content
Glama

Add snow report

add_snow_report

Only relay a report from a person who is at, or was just at, the resort. Never invent a report. The report goes live immediately and is labelled as relayed via an AI assistant.

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": {
      "resort": "<resort>",
      "text": "<text>"
    },
    "name": "add_snow_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
textYes
ratingNo
resortYesResort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)
observed_todayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resort / description
      Added value: +"Resort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds meaningful behavior beyond that: the report is published immediately and publicly labelled as relayed via an AI assistant, which tells the agent the effect is instantaneous and attributable. It still omits whether the submission can be edited or removed afterwards.

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?

Three short sentences, each carrying a distinct rule (source constraint, anti-fabrication rule, publishing consequence). Nothing is wasted and the most important constraint is front-loaded.

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?

The description covers the behavioral consequence of the call well, which matters for a mutation tool with no output schema. However, with 5 parameters at 20% schema coverage and no explanation of tags, rating, or observed_today, an agent could easily misuse or omit these fields; that is a real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% – just the resort field is documented. The description explains nothing about text, tags, rating, or observed_today, so the four undocumented parameters rely entirely on their names and constraints. For a 5-parameter tool, this leaves a substantial gap the description does not compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses 'relay a report' and 'the report goes live immediately', which implies a submission/creation action for snow reports, but it never states plainly that this tool adds a snow report to a resort. The title supplies most of the purpose, so an agent can infer it, but the description alone is more of a constraint statement than a purpose statement.

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?

It gives an explicit precondition for calling: only relay reports from someone at or recently at the resort, never invent one. That is clear when-to-use guidance, though it names no alternatives and does not say what to do instead when no first-hand report exists (e.g., point to get_snow_reports or get_conditions).

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