Skip to main content
Glama

Dealectics deal verdict

Read a watch

get_watch
Read-onlyIdempotent

State of a watch created with create_watch: awaiting confirmation, active or stopped, and how many alerts were sent.

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": {
      "watch_id": "<watch_id>"
    },
    "name": "get_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
watch_idYesThe watch_id that create_watch returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / watch_id / description
      Added value: +"The watch_id that create_watch returned."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful detail of which state values and the alert count come back, but says nothing about error behavior or freshness of the alert count.

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?

One front-loaded sentence with no filler; the resource, the provenance and the returned fields all arrive in the first clause.

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?

With no output schema, the description correctly shoulders the burden of describing return values by enumerating the possible states and the alert count. A one-param, fully annotated read tool needs little more, though a note on unknown-id behavior or state transitions would close the last gap.

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% and the single parameter is documented as 'The watch_id that create_watch returned.' The description merely echoes that provenance, adding no format or sourcing detail beyond the schema, so baseline 3 applies.

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 the specific resource (a watch) and enumerates what is returned: the states awaiting confirmation/active/stopped plus the alert count. It also ties the resource to create_watch, which lets an agent distinguish it from the create/stop siblings, though the read-vs-mutate contrast with stop_watch is only implied.

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

Usage Guidelines3/5

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

Mentioning 'created with create_watch' implies the usage context (poll after creating a watch), but there is no explicit when-to-use, no guidance on polling cadence or when-not to call it, and no statement about what happens for an unknown watch_id.

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