Skip to main content
Glama

agent-tool-finder

by io.github.ciinkwia
OverviewDiscussionsAdmin

send_feedback

Report a bug, missing feature, wrong data, or a slow call on clink's shop — for a call you already made, not a new capability request (use request_agent_tool for that). Read the same day; if it's a real bug it gets fixed and you're told. Free.

Input Schema

NameRequiredDescriptionDefault
kindYes
routeNoOptional. The endpoint path you called, e.g. /x/search.
notifyNoOptional. An email address or https webhook URL to ping when it's fixed.
wantedNoOptional. What you expected/wanted instead, up to 2000 chars.
receipt_idNoOptional. The rcpt_… id from the receipt block of the paid call you're reporting — links this to the exact call.
request_urlNoOptional. The exact call that went wrong, including query params.
tx_or_buyerNoOptional. Your wallet address or a transaction hash for the call, if you have it — helps link this to the actual failed call.
what_happenedYesWhat happened, 3-2000 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "bug",
-  "missing_feature",
-  "wrong_data",
-  "slow",
-  "other"
-]New value: +[
+  "bug",
+  "missing_feature",
+  "wrong_data",
+  "slow",
+  "refund",
+  "other"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / receipt_id
      Added value: +{
+  "description": "Optional. The rcpt_… id from the receipt block of the paid call you're reporting — links this to the exact call.",
+  "type": "string"
+}
  3. Added

TDQS

A4.4/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 delivers real behavioral context: read same-day SLA, remediation on confirmed bugs, notification back to the caller, and no cost ('Free'). It omits auth requirements and what happens for edge kinds (e.g. refund), keeping it just short of a 5.

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 core action and the sibling exclusion, followed by turnaround/resolution and cost. Every clause carries distinct, useful information with 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?

For a feedback-submission tool with no output schema and no annotations, the description supplies purpose, routing, latency, outcome, and price. It stops short of covering auth prerequisites or the refund path, so it is strong but not fully exhaustive.

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 88%, so the schema already documents route, notify, wanted, receipt_id, request_url, tx_or_buyer, and what_happened. The description only gestures at the 'kind' values (bug, missing feature, wrong data, slow) and omits the enum's refund/other, adding little 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?

Names a specific verb (report) and resource (bug/missing feature/wrong data/slow call), scoping it to clink's shop. It actively distinguishes itself from the sibling request_agent_tool, so an agent can separate the two without opening either schema.

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?

Gives explicit when-to-use ('for a call you already made') and when-not ('not a new capability request'), and names the alternative tool (request_agent_tool) for the excluded case. This is exactly the routing guidance an agent needs.

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

All agent-tool-finder toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources