Crawlora MCP

trustmrr_startup

Read-only

Fetch TrustMRR startup details, including verified revenue, MRR, marketplace status, technology stack, and AI summary. Use trustmrr_startups to browse startups or trustmrr_marketplace for listings and deals.

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": {
      "slug": "<slug>"
    },
    "name": "trustmrr_startup"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Resource slug.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, external-facing read. The description adds the profile of returned content, but no auth requirements, rate limits, or failure behavior when a slug is unknown. Adequate given the annotations carry the safety profile.

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 sentences, front-loaded with the purpose before the routing hint, and every clause earns its place—no filler or repetition of the tool name.

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?

An output schema exists, so return values need not be described, and the description still usefully previews what the record contains. What's missing is minor: no note on slug acquisition or behavior for a non-existent slug, but nothing blocks correct invocation.

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?

There is a single required slug parameter with 100% schema description coverage, so the baseline is 3. The description implies the slug identifies a specific startup but adds no format, uniqueness, or lookup guidance beyond the schema's generic 'Resource slug.'

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?

States a specific verb (Fetch) and resource (TrustMRR startup details) and enumerates the returned content (verified revenue, MRR, marketplace status, tech stack, AI summary). It explicitly distinguishes itself from the sibling trustmrr_startups and trustmrr_marketplace, so an agent can route without opening the schema.

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?

Names two alternatives and the conditions that select them: trustmrr_startups for browsing and trustmrr_marketplace for listings/deals, implying this tool is for a single known startup. No explicit prerequisite (e.g., how to obtain a valid slug) and no negative case beyond the routing hints.

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

All Crawlora MCP 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?