Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

enterprise-research

[x402 paid: $49.990 USDC on Base] Enterprise tier: a custom research report or data pipeline built to your spec and delivered within 24h (crypto, markets, tech). Includes 100 AI calls, raw JSON data, executive summary, and the on-chain receipt. One payment, real delivery. tools/call returns the live payment challenge.

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": "enterprise-research"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 well: it discloses the exact price ($49.990 USDC), the chain (Base), the 24h delivery window, what is included (100 AI calls, raw JSON, executive summary, on-chain receipt), and crucially that 'tools/call returns the live payment challenge.' It does not cover failure modes, refunds, or how the payment proof is attached on retry.

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?

Dense and front-loaded: price and chain lead, then deliverables, then delivery mechanics. 'One payment, real delivery' is slightly promotional filler, but the rest of the sentences each add distinct information.

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?

The description covers price, scope, inclusions, turnaround, and the payment challenge, which is substantial for a zero-parameter tool with no output schema. However, it says the report is 'built to your spec' while exposing no parameters for supplying that spec and giving no pointer to how to provide it, leaving a real operational gap.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description adds no param meaning because none exists, which is appropriate.

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 concrete deliverable ('custom research report or data pipeline'), a tier ('Enterprise'), a domain scope ('crypto, markets, tech'), and a turnaround ('within 24h'). The tier and price framing implicitly separates it from the cheaper pack siblings, though it never names an alternative outright.

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?

Usage is implied by naming the tier ('Enterprise') and the deliverables, so an agent can infer this is the premium option, but there is no explicit when-to-use versus tool_ai_research-pro or the /pack/buy siblings. No when-not guidance or exclusions are given.

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