Skip to main content
Glama

Send feedback

eurobase_submit_feedback

Sends feedback about Eurobase itself to the Eurobase team in the user's name, into the same inbox as the dashboard Feedback button. kind is bug when Eurobase behaves unexpectedly or an error message or the documentation is unclear, and suggestion for something missing. Not for problems in the user's own application code. Send only what the user agrees to share. In message, describe what was done, what was expected and what happened, and quote the requestId of a failed call; never include secrets, tokens, environment variable values or personal data. message is at most 5000 characters. projectId names a permitted project the report is about; deploymentId names one of its deployments and requires projectId. At most 10 reports a minute. Each call sends one report, so repeating it sends another. Returns the report ID.

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": {
      "kind": "<kind>",
      "message": "<message>"
    },
    "name": "eurobase_submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
messageYes
projectIdNo
deploymentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare the mutation and non-idempotency profile, so the bar is lower, and the description genuinely adds to them: the 10-reports-per-minute rate limit, the destination inbox, the 'in the user's name' attribution, the confidentiality constraints, and the return value. The only real gap is that it doesn't say what happens on validation failure or how errors surface.

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?

Front-loaded with purpose, then usage, then parameter guidance, and every clause carries information that isn't in the schema or annotations. It is a single dense block though, with security warnings and parameter rules interleaved, which makes it slower to scan than a short bulleted structure would be.

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?

For a four-parameter mutation tool with no output schema, the definition covers what it does, when to use it, when not to, rate limits, non-idempotency, content requirements, parameter dependencies, and the return value (the report ID). An agent has everything needed to call it correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero schema description coverage the description carries the burden, and it does: it explains the semantics of both enum values, the 5000-character message limit, the expected message content structure, what projectId and deploymentId refer to, and the dependency that deploymentId requires projectId. It doesn't mention the prj_/dep_ prefix patterns or that projectId is optional, but those are visible in the schema.

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 and resource ('Sends feedback about Eurobase itself to the Eurobase team') and pins the scope twice: feedback about the platform, not the user's application. That scope note alone distinguishes it from every diagnostic sibling in the catalog.

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 enumerates when to use each kind ('bug when Eurobase behaves unexpectedly or an error message or the documentation is unclear, and suggestion for something missing') and gives an explicit exclusion ('Not for problems in the user's own application code'). It also adds an authorization rule ('Send only what the user agrees to share'), which is exactly the gate an agent needs before calling.

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.