Skip to main content
Glama
Sign In

PaidRouter

by com.paidrouter
OverviewDiscussionsAdmin

Request coverage

request_route

When the owner needs a provider, method, country or corridor PaidRouter doesn't cover yet (get_fees came back empty, or compare_send_money doesn't know the corridor), send what they need. PaidRouter records it, counts it on https://paidrouter.com/coverage, and adds the most-requested coverage every week with the date. Returns what is covered today that comes closest.

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": {
      "what": "<what>"
    },
    "name": "request_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the owner is trying to do
noteNoAnything that helps, e.g. the amount or how often
whatYesProvider, method or corridor, e.g. 'QuickBooks Payments', 'Wise → Philippines', 'paying a supplier by ACH', 'GBP receiving'
countryNoCountry or currency involved, if any

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 does disclose the key side effect that isn't obvious from the schema: the request is recorded and publicly counted at paidrouter.com/coverage, and the most-requested coverage is added weekly. It also states the return value ('what is covered today that comes closest'). It stops short of saying whether requests are idempotent, whether the owner is notified, or whether the public count exposes any owner identity.

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 sentences, all load-bearing, with the triggering condition front-loaded before the side-effect and return-value details. The phrasing 'send what they need' is the only soft spot; everything else is dense and purposeful.

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?

No output schema and no annotations, so the description must cover behavior and returns — it does both, stating that the closest currently-covered option is returned. Parameter documentation is fully handled by the schema. Missing only secondary details like rate limits, auth requirements, or whether duplicate requests are deduplicated.

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% and the schema already supplies concrete examples for 'what', the 'kind' enum, and the 'note'/'country' fields. The description adds no additional syntax or constraint guidance for the four parameters beyond the general 'send what they need', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this is a coverage-request tool: it names the trigger (a provider, method, country or corridor PaidRouter doesn't cover) and the outcome (PaidRouter records it and adds the most-requested coverage weekly). The verb 'send what they need' is slightly indirect compared with the title, but the resource and scope are unmistakable and clearly distinct from the sibling lookup 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 gives explicit trigger conditions with named alternatives: use this when get_fees comes back empty or compare_send_money doesn't know the corridor. That routes the agent away from the sibling tools precisely at the moment they fail, which is exactly the when-to-use guidance that matters here.

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

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