Skip to main content
Glama

submit_feedback

Leave a suggestion about how to make this knowledge base more useful or accessible to AI agents. Use for missing content, errors, format issues, accessibility, praise, or other suggestions. Submissions are reviewed before they appear on the public board. Do not include off-site links in the message.

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": {
      "category": "<category>",
      "message": "<message>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional site path or URL on this knowledge base that the feedback is about
messageYesThe suggestion or comment, at most 2000 characters. No off-site links.
categoryYesKind of feedback
agent_urlNoOptional http(s) URL for the calling agent
agent_nameNoOptional name of the calling agent or client

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does add real behavioral facts: submissions are moderated ('reviewed before they appear on the public board') and off-site links are prohibited. However, for a mutation tool it omits whether authentication is required, whether submissions are editable or withdrawable, and any rate limiting, leaving meaningful gaps.

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 short sentences, front-loaded with purpose before constraints, with no filler. The category enumeration in the second sentence somewhat duplicates the enum in the schema, which is the only avoidable weight.

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 feedback-submission tool with no output schema and no annotations, the description covers purpose, triggers, and moderation behavior. It stops short of telling the agent what a successful submission returns or whether identity fields affect the outcome, which leaves an agent guessing about the result of the call.

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%, so all five parameters are already documented in the schema, which sets the baseline at 3. The description reinforces the message constraint ('Do not include off-site links') but adds nothing about page, agent_url, or agent_name beyond what the schema states.

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?

Specific verb and resource ('Leave a suggestion about how to make this knowledge base more useful or accessible to AI agents'), and the scope is unmistakably distinct from the read-only siblings get_answer and search_questions. An agent can tell immediately that this is a write-a-feedback action rather than a retrieval call.

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

Usage Guidelines4/5

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

It enumerates concrete triggers ('missing content, errors, format issues, accessibility, praise, or other suggestions'), which tells the agent when to reach for it. There is no explicit when-not guidance or mention of alternatives, though the sibling tools are retrieval-oriented so overlap is minimal; the category list also largely restates the enum.

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