Skip to main content
Glama

fundinglens__best

For one symbol, the venues with the highest and lowest funding. 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/fundinglens/best

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": {
      "symbol": "<symbol>"
    },
    "name": "fundinglens__best"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
      +  "symbol"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / symbol
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / symbols
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

A3.5/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 provides important behavioral details: cost ($0.01 per call), payment mechanism (x402 in params._meta), and HTTP GET endpoint. It does not cover rate limits, error behavior, or explicitly state read-only semantics beyond GET.

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?

Two tight sentences: the purpose is front-loaded, followed by essential cost and endpoint information. No unnecessary wording.

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

Completeness3/5

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

For a simple paid endpoint with no output schema or annotations, the description includes critical payment and HTTP details but omits the symbol format and does not specify the returned venue fields. Adequate but with clear gaps.

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?

Schema coverage is 0%, so the description must compensate, but it only says 'For one symbol' without defining the expected symbol format or examples. This adds little beyond the schema's required string field.

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?

States the specific operation: for one symbol, return the venues with the highest and lowest funding. The scope is clear, though it does not explicitly contrast with sibling fundinglens__rates.

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

Usage Guidelines3/5

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

The phrase 'For one symbol' implies the single-symbol use case, but there is no explicit when-to-use guidance, exclusion, or named alternative such as fundinglens__rates.

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