Skip to main content
Glama
Sign In

Synthex Forge — x402 Paid Agent Services

by com.synthexforge.x402
OverviewDiscussionsAdmin

Search Capabilities

search_capabilities
Read-onlyIdempotent

Search every tool by keyword across all domains and return the matches with their domain, so you can find the tool before you commit to a domain.

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": {
      "query": "<query>"
    },
    "name": "search_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matches to return. Defaults to 20.
queryYesThe words to search for in a tool's name, summary or description.

Output Schema

NameRequiredDescriptionDefault
queryNoThe query that was run.
matchesNo
match_countNoHow many tools matched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds the important scope fact that the search spans all domains, but says nothing about match behavior (ranking, substring vs. token matching, why results may be capped), which is the one behavioral trait an agent would actually want here.

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?

A single sentence with the scope claim front-loaded and the motivation trailing it. Nothing is repeated from the title and no words are wasted.

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?

With an output schema present, return values need not be explained, and annotations plus full schema coverage handle safety and parameters. The only remaining gap is search semantics (how a query is matched, whether results are ranked), which would help an agent phrase queries correctly.

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 100%, so query and limit are already documented, including the default of 20. The phrase 'by keyword' is the only added signal, hinting at simple keyword matching rather than query syntax, which is a marginal contribution over the schema.

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 names a specific verb (search) and resource (every tool across all domains) and states the return shape ('matches with their domain'). It implies differentiation from domain-scoped discovery, but it never names list_domains or describe_capability, so the boundary is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The clause 'so you can find the tool before you commit to a domain' clearly states the situation that selects this tool: unknown target domain. There are no explicit exclusions or named alternatives for the case where the domain is already known, which keeps it below a 5.

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

All Synthex Forge — x402 Paid Agent Services 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