Skip to main content
Glama

Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402)

Angel Picks: where to get it (free)

recommend
Read-only

Free: describe what your agent needs outside paid APIs — hosting or a database, GPUs, a product to buy, a hotel or tour, a domain, website or online store, a human freelancer, a voice or AI tool, paying an invoice abroad, cheaper electricity — and get up to 5 providers ranked by match only, each with a link and a ready preflight check. Partner links are marked (tracked) and disclosed. After: preflight the link before paying; paid APIs and agents: exchange_route.

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": {
      "need": "<need>"
    },
    "name": "recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the result cap of 5, that ranking is by match only, that every result carries a link plus a preflight check, and that partner links are tracked and disclosed. It does not say what happens when nothing matches, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading 'Free:' framing and the trailing workflow pointer are well front-loaded and back-loaded. However, the middle is a long em-dash enumeration of use cases that is dense to parse, and the value-per-word is lower there than elsewhere in the description.

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?

There is no output schema, and the description compensates by explaining the return shape: up to 5 ranked providers, each with a link and a preflight check. Combined with the disclosure of tracked partner links and the recommended follow-up call, an agent has enough to invoke and act on results. Only the empty-result case and limit default are unstated.

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 0%, so the description carries the burden for all three parameters. It partly does: the category examples (hosting, database, GPUs, product, hotel or tour, domain, website, freelancer, voice or AI tool, invoice abroad, electricity) map onto the enum values, and 'up to 5' hints at the limit bound. But `need` format and length limits and the meaning of `limit` are never stated, so compensation is incomplete.

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 states a concrete outcome: describe a need and get up to 5 providers ranked by match, each with a link and a preflight check. That is specific enough to distinguish it from exchange_route, which it explicitly names as the paid-API counterpart. The long category enumeration adds scope detail but blurs the core verb-and-resource statement.

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 states the selection condition explicitly: use this for needs outside paid APIs, and use exchange_route for paid APIs and agents. It also gives the follow-on step, 'preflight the link before paying', which tells the agent how this tool fits into a larger workflow.

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.

Resources