Skip to main content
Glama
Sign In
EasyShiftPlan MCP Bridge

EasyShiftPlan MCP Bridge

by ray999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Check an optional feedback reply

get_demo_feedback_reply
Read-onlyIdempotent

Retrieve the status or administrator reply for a previously submitted public-demo observation using the exact feedback_reference returned at submission; skip this optional lookup if no feedback was submitted.

Instructions

Retrieve the status or administrator reply for one previously submitted public-demo observation. Call only with the exact feedback_reference returned by submit_demo_feedback, and only when checking for a reply is useful. If no feedback was submitted, skip this optional tool. Never invent a reference or poll repeatedly.

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": {
      "feedback_reference": "<feedback_reference>"
    },
    "name": "get_demo_feedback_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedback_referenceYesExact 24-character reference returned by a successful submit_demo_feedback call. Required for this optional lookup; never invent it.

Output Schema

NameRequiredDescriptionDefault
replyNo
statusYes
messageYes
next_actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the tool is optional, must not be polled repeatedly, and must not be called with fabricated input. It stops short of describing what a not-yet-answered status looks like, keeping it below a 5.

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?

Three sentences, front-loaded with the purpose before the constraints, and each sentence carries a distinct rule. 'Only when checking for a reply is useful' is slightly soft but is immediately firmed up by the concrete skip and no-polling instructions.

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?

An output schema exists, so return values need no explanation, and the description covers the remaining gaps an agent would face: input provenance, optionality, and the do-not-poll rule. Nothing needed to invoke this correctly is missing.

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 parameter already documents its 24-hex-char pattern and origin in submit_demo_feedback. The description's restatement of provenance and the 'never invent it' warning adds emphasis but no new syntax or format detail, so the baseline 3 is correct.

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?

States a specific verb ('Retrieve') and resource ('status or administrator reply for one previously submitted public-demo observation'), and implicitly distinguishes itself from the sibling submit_demo_feedback, which produces the reference this tool consumes. An agent can tell the write path from the read path without opening either schema.

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 states when to call ('only when checking for a reply is useful'), when not to call ('If no feedback was submitted, skip this optional tool'), and two concrete anti-patterns ('Never invent a reference or poll repeatedly'). Alternatives and exclusions are both named.

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

Deploy Server

Other Tools