Skip to main content
Glama
Sign In

CoinPaprika

by com.coinpaprika.mcp
OverviewDiscussionsAdmin

submitFeedback

Report a problem or gap back to the CoinPaprika MCP maintainers: call it when you got stuck, a response was unexpected, information you needed was missing, or a tool did not behave as documented. Use when the user says 'this is wrong', 'report this', 'that did not work'. Low friction, partial feedback is welcome, and every submission is read.

Input Schema

NameRequiredDescriptionDefault
goalYesREQUIRED: What you (or the user behind you) were trying to accomplish.
expectedNoOPTIONAL: What you expected to happen.
observedNoOPTIONAL: What actually happened.
severityNoOPTIONAL: How badly this affected your task. Default 'minor'.minor
blocked_atNoOPTIONAL: Tool name or step where you got stuck.
attempted_toolsNoOPTIONAL: List of tool names you called, in order, before submitting this feedback.

Output Schema

NameRequiredDescriptionDefault
okYesTrue if the feedback row was persisted.
messageYes
severityNo
tracking_idNoStable id agents can reference in follow-up submissions; null if persistence failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / message / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / ok / type
      Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
    • addedOutput schema / properties / severity / anyOf
      Added value: +[
+  {
+    "enum": [
+      "blocker",
+      "major",
+      "minor",
+      "nit"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / severity / enum
      Removed value: -[
-  "blocker",
-  "major",
-  "minor",
-  "nit"
-]
    • removedOutput schema / properties / severity / type
      Removed value: -"string"
  2. Changed3 schema fields changed
    • addedInput schema / properties / attempted_tools / items / maxLength
      Added value: +100
    • addedInput schema / properties / attempted_tools / maxItems
      Added value: +50
    • addedInput schema / properties / blocked_at / maxLength
      Added value: +200
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "True if the feedback row was persisted.",
+      "type": "boolean"
+    },
+    "severity": {
+      "enum": [
+        "blocker",
+        "major",
+        "minor",
+        "nit"
+      ],
+      "type": "string"
+    },
+    "tracking_id": {
+      "description": "Stable id agents can reference in follow-up submissions; null if persistence failed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ok",
+    "message"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, non-destructive, non-idempotent submission tool, and the description adds that partial feedback is welcome and every submission is read. It does not discuss privacy, rate limits, or exactly how submissions are processed, but it adds useful behavioral context beyond the 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?

The purpose is front-loaded in the first sentence, and the second sentence efficiently adds usage triggers and tone. The description is appropriately sized with no filler.

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 feedback-submission tool with full schema documentation, rich annotations, and an output schema, the description provides enough context to call it correctly. The agent knows when to use it, what to report, and that partial feedback is acceptable.

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 description coverage is 100%, so the input schema already documents all six parameters, including the required goal and optional expected/observed/severity fields. The description reinforces low-friction submission but adds no parameter-specific syntax or format details beyond 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?

The description states a specific action and target: report a problem or gap back to the CoinPaprika MCP maintainers. It is clearly distinguishable from all sibling tools, which are data-retrieval tools rather than feedback submission tools.

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?

It explicitly lists when to call it: when stuck, when a response was unexpected, when needed information was missing, or when a tool did not behave as documented. It also names user phrasings such as 'this is wrong', 'report this', and 'that did not work', leaving little inference required.

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

All CoinPaprika 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