Skip to main content
Glama

Check staff reply

check_reply
Read-onlyIdempotent

Check if GYOTAK staff has replied to a previously submitted inquiry.

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": {
      "inquiryId": "<inquiryId>"
    },
    "name": "check_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
inquiryIdYesInquiry ID (e.g. "INQ-042")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the precondition of a prior inquiry; it says nothing about what the check returns (a boolean flag, a message, a status code) or how recently it polls.

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?

A single front-loaded sentence with no filler; the core action and object come first. It is perhaps slightly terse given the undefined return value, but nothing in it is wasted.

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?

For a simple one-parameter read tool with full annotation coverage, the description is nearly sufficient. The notable gap is the absence of an output schema combined with no description of what "check" yields, leaving the agent to guess whether it gets a boolean or reply content.

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 100% and the single inquiryId parameter is documented with a concrete example ("INQ-042"). The description adds no format or validation detail beyond what the schema already supplies, so the baseline of 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?

States a specific verb (check) and resource (staff reply on a previously submitted inquiry), which is unambiguous. It implicitly distinguishes itself from ask_gyotak/contact_gyotak by describing a status check rather than submission, but never names those siblings explicitly.

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?

The phrase "previously submitted inquiry" implies a prerequisite (an inquiry must already exist) and that this is a follow-up check. However, there is no explicit when-to-use guidance, no statement about when not to use it, and no named alternative for submitting an inquiry in the first place.

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