API Plan Finder

Pass on what the person thought of a plan or ranking

send_feedback

Use this when: after you gave the person an API plan or ranking from this service, they say what they think of it (useful or not, a price or fact that looks wrong, something missing, the plan they chose), or you work for a provider listed here and a fact about your own plans looks wrong, missing or outdated (include the official page in source_url). Pass the gist in one call: from, kind, and optionally the offer_id, what it is about, and a short message. Do not use this to ask for a field, provider, condition or plan to be covered (use request_coverage), and do not include a name, e-mail address, link or other personal information. Nothing is returned beyond the receipt, and nothing sent here changes the published facts: they change only after we re-check the official page. Example: from user_assistant, kind wrong_fact, about price, message "the page says 49 a month".

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": {
      "from": "<from>",
      "kind": "<kind>"
    },
    "name": "send_feedback"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Who is sending: user_assistant (an assistant passing on what its user said) or provider (an assistant of a provider listed here, about its own plans).
`kind`	Yes	What the person said: useful, not_useful, wrong_fact (a price or fact that looks wrong), missing (something they needed was not there), outdated (a price, plan or condition has changed), chose_plan (the plan they chose), or other.
`about`	No	Optional. What the remark is about: answer, plan, price, condition, ranking, coverage or other.
`message`	No	Optional. The gist of what the person said, in one or two short sentences (at most 300 characters). No name, contact detail or other personal information.
`offer_id`	No	Optional. The offer_id from this service's result that the remark is about.
`provider`	No	Only with from provider. Optional. The provider name (at most 80 characters).
`source_url`	No	Only with from provider. Optional. One https address of the provider official page that shows the fact (at most 300 characters).

Output Schema

Name	Required	Description	Default
`kept`	Yes
`note`	No
`received`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (which only mark it non-read-only and non-destructive), the description discloses that the tool is advisory only: 'Nothing is returned beyond the receipt, and nothing sent here changes the published facts: they change only after we re-check the official page.' It also states a privacy rule (no name, e-mail, link or other personal information) and a provider-specific requirement to include the official page in source_url.

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?

It is front-loaded with the triggering condition and the prohibition before the mechanics, so an agent can stop reading early once it knows the tool does not apply. It is one dense paragraph, and the closing example partly restates enum values already in the schema, which keeps it from a 5.

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 7-parameter write-style tool with an output schema, the description covers who sends, when to send, when not to, privacy constraints, provider-side source requirements, and the effect on published data. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-field meaning the schema does not encode: the 'from provider' case must include the official page in source_url, and the payload should be passed 'in one call' as from, kind, plus optional offer_id/about/message. The worked example also clarifies the intended granularity of 'message'.

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 opening clause names a specific action (pass on what the person said) and its object (a plan or ranking from this service), and the description explicitly names the sibling it is not (request_coverage). An agent can distinguish it from share_ranking or request_coverage 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 Guidelines5/5

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

It gives an explicit trigger ('after you gave the person an API plan or ranking... they say what they think of it'), a second trigger for provider-side corrections, and an explicit exclusion with a named alternative ('Do not use this to ask for a field, provider, condition or plan to be covered (use request_coverage)').

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

All API Plan Finder tools Inspect

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

Need Help?