Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trustmrr_category

Retrieve a TrustMRR category by slug to see its listed startups with MRR, total and last-30-day revenue, URLs, descriptions, and on-sale flags.

Instructions

Get TrustMRR category detail. Returns one TrustMRR category by slug (lowercase letters, digits and hyphens, for example saas) with the startups listed in it. Each startup has its name, slug, URL, description, current MRR, total revenue and last-30-days revenue, all in USD, plus the on_sale flag for startups listed for sale. Valid slugs come from /trustmrr/categories.

Input Schema

NameRequiredDescriptionDefault
slugYesTrustMRR category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose substantial behavioral context: it enumerates the returned startup fields (name, slug, URL, description, current MRR, total revenue, last-30-days revenue, on_sale flag) and states all monetary values are in USD. It does not address pagination, result limits, or whether this is strictly read-only, but the return-shape disclosure is genuinely useful.

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?

Three tight sentences, front-loaded with the purpose, then the identifier format, then the payload. Every sentence contributes new information; the field enumeration earns its length by standing in for a missing output schema.

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 single-resource fetch with no annotations and no output schema, the description covers purpose, identifier format, identifier source, and return contents, which is close to complete. The only gap is any statement about how many startups are returned or whether that list is paginated.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real constraint detail the schema lacks: 'lowercase letters, digits and hyphens, for example `saas`'. That format rule plus a concrete example improves the agent's ability to construct a valid slug over the bare schema text 'TrustMRR category slug'.

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 a specific verb+resource ('Get TrustMRR category detail... Returns one TrustMRR category by slug with the startups listed in it') and pins down the return payload closely enough that an agent can tell it apart from a startup-level fetch. The reference to /trustmrr/categories as the slug source softly differentiates it from the category-listing sibling, but no explicit contrast with trustmrr_startup or trustmrr_startups is drawn.

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 only implied: 'Valid slugs come from /trustmrr/categories' tells the agent to source the identifier from the sibling tool, which is a real prerequisite hint. However, there is no explicit when-to-use guidance or when-to-prefer-an-alternative statement versus trustmrr_startup, trustmrr_startups, or trustmrr_marketplace.

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

Deploy Server

Other Tools