ResearchSprint

order_competitor_analysis

Order a competitor analysis report (1,500+ words, same-day delivery). Pay $49 USDC on Ethereum mainnet.

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": {
      "topic": "<topic>",
      "email": "<email>"
    },
    "name": "order_competitor_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	Email address to receive the report
`topic`	Yes	Your market and competitors to analyze

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description must disclose behavioral traits. It reveals that the tool requires payment ($49 USDC on Ethereum mainnet) and delivery time (same-day), which are critical. However, it does not mention what happens after ordering (e.g., confirmation, failure modes).

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?

The description is a single, efficient sentence that conveys the essential information without filler. Every word adds value.

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?

For a simple ordering tool with two parameters, the description covers the critical operational details (cost, delivery time, word count). It could be more complete by specifying the report format or delivery method, but it is adequate for an agent to understand the core functionality.

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?

Since schema description coverage is 100%, the baseline is 3. The description adds overall context but does not provide additional detail on the parameters beyond what the schema already gives.

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

Purpose5/5

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

The description clearly states the action ('Order'), the resource ('competitor analysis report'), and key attributes (1,500+ words, same-day delivery, $49 USDC payment). This distinguishes it from sibling tools like order_blog_post or order_market_research.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios, or when not to use it. The payment information is given but not contextualized as a usage condition.

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

All ResearchSprint tools Inspect

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

Need Help?