Skip to main content
Glama

feedback

Rate a host reply from 1 to 5 with fixed tags that tune your own future tone, length, theme and activity. Requires session. Optional text is moderated and discarded.

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": {
      "session": "<session>",
      "rating": "<rating>",
      "tags": "<tags>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes
textNo
ratingYes
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the mutation profile (readOnly=false, destructive=false, non-idempotent); the description adds genuinely non-obvious context: the feedback persists as a tuning signal for the agent's own future output, and submitted text is moderated then discarded. It does not explain whether prior ratings are overwritten, but the added data-handling detail goes well beyond annotations.

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?

Two tight sentences; the core action and its effect are front-loaded, and the session prerequisite and text handling follow as needed qualifiers. No filler.

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?

Given four parameters, no output schema, and thin schema descriptions, the description covers requirement, effect, and data handling adequately. It falls short only on the meaning/selection logic for the tag vocabulary, which an agent must guess.

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 25% (only session is documented). The description compensates partially by clarifying that text is optional and discarded, and restating the 1-5 rating bound, but the many enumerated tags (scene, story, ember-shrine, koso-tower) are opaque and never explained — the highest-value gap for correct invocation.

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 (rate) with a bounded scale (1-5), the object (a host reply), and the effect (tags tune future tone, length, theme, activity). Nothing in the sibling list (host, concierge, tip) could be confused with it.

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?

It implies the trigger context (rating a host reply) and states the hard prerequisite 'Requires session', but never says when not to use it or points to an alternative like tip or leave_note for non-tone feedback.

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