Skip to main content
Glama

pageaudit__funding

Web page intelligence for agents: audit pages, check SEO metadata, preflight URL liveness, monitor pages for changes, vet x402 sellers, and compare perp funding rates across Binance/OKX/Bybit/Gate. $0.01/call USDC on Base; free real previews. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/pageaudit/funding

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pageaudit__funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful operational facts: the price ($0.01 USDC on Base, eip155:8453), the x402 payment location in params._meta["x402/payment"], and the HTTP endpoint. That is real value the schema cannot provide. However, it says nothing about the returned data shape, rate limits, or freshness of the funding rates, and the payment path references a _meta field that does not exist in the input schema.

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

Conciseness2/5

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

The description is a single overloaded catalog sentence spanning six unrelated capabilities, so the relevant clause is buried rather than front-loaded. Pricing is then stated twice in near-identical wording ('$0.01/call USDC on Base' followed by '$0.01 per call in USDC on Base (eip155:8453)'), which is redundant rather than informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and an undocumented optional parameter, the description needs to explain the argument and what comes back. It instead supplies payment and endpoint mechanics while leaving the single input unexplained and the funding-rate output (pairs, exchanges, timestamps) undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter, 'url', at 0% description coverage, so the description must explain it and does not mention it at all. Worse, a 'url' argument is unintuitive for an exchange funding-rate comparison tool, leaving the agent with no idea whether to pass an exchange API URL, a page URL, or omit it (it is optional per the schema).

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

Purpose2/5

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

The actual purpose appears only as the last item in a list: 'compare perp funding rates across Binance/OKX/Bybit/Gate'. The lead sentence frames the tool as a general page-intelligence utility ('audit pages, check SEO metadata, preflight URL liveness, monitor pages for changes, vet x402 sellers'), most of which describes sibling tools like pageaudit__audit or pageaudit__preflight. An agent skimming the opening will form the wrong impression of what this tool returns.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative such as funding_rates__spread or funding_rates__carry even though the sibling list makes them obvious competitors. The closest thing to routing is the mention of four exchanges, which does not tell an agent when to pick this over the other funding_rates tools.

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