Skip to main content
Glama
Sign In

Nutrients

by io.prospre
OverviewDiscussionsAdmin

feedback_status

Read progress of your own feedback, free: status, canonical issue or duplicate, fix PR and regression test, or decline reason. No other reporter text or identity is exposed.

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_id": "<feedback_id>"
    },
    "name": "feedback_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedback_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it establishes the operation is a read, that it is free, that it is scoped to the caller's own feedback, and that no other reporter's text or identity is exposed. It stops short of stating what happens for an unknown or foreign feedback_id (error vs empty), which is the main remaining behavioral gap.

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, front-loaded with the action and the free/no-cost fact, followed by the enumeration of outcomes. Nothing is redundant and nothing needed for selection is buried.

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?

For a one-parameter read tool with no output schema, the description usefully previews the return categories, which the absent output schema would otherwise leave blank. Missing only edge-case behavior (nonexistent or unauthorized ID) and how to obtain feedback_id.

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?

A single feedback_id with 0% schema description coverage, so the schema gives only type and bounds. The description adds the meaningful constraint that the ID must refer to the caller's own feedback, but does not say how the ID is obtained or what happens when it is invalid or not owned.

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+resource ('Read progress of your own feedback') with an explicit scope limitation ('your own'), and enumerates the outcomes it returns (status, canonical issue or duplicate, fix PR/regression test, decline reason). This is clearly distinguishable from a submission-style sibling like 'feedback' without opening any schema.

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?

'free' and 'your own feedback' imply the usage envelope (no cost, restricted to the caller's own submissions), which is useful. However, there is no explicit when-to-use/when-not guidance and no named alternative for other cases, so usage is only implied.

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

All Nutrients toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources