Skip to main content
Glama

ShowMRR

Compare startups

compare_startups
Read-onlyIdempotent

Compare the current MRR and growth of 2 to 5 startups side by side, with the verification status of each figure.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_startups"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slugs / items / description
      Previous value: -"ShowMRR startup slug, the last part of https://showmrr.com/startup/<slug>. Use search_startups to find it."New value: +"ShowMRR startup slug: the last part of a startup page address on showmrr.com, lowercase letters, digits and hyphens."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing that each returned figure carries its verification status, which the agent could not know from annotations alone. It does not cover edge behavior such as an invalid or unknown slug, which keeps it from a 5.

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?

A single tight sentence with zero filler, front-loading the operation, target, compared metrics, and the verification-status detail in one pass.

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 one-parameter, read-only comparison tool with no output schema, the description covers what is compared, how many entities, and a key property of the results. A note on slug validity handling or response shape would complete it, but nothing essential for invoking it correctly is missing.

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?

The only parameter is slugs, and the description's '2 to 5 startups' merely restates the schema's minItems/maxItems constraints rather than adding meaning. The slug format itself is documented in the schema's item description, not the tool description, so the description does little to compensate for the low parameter-level coverage.

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 specific verb (compare), resource (startups), the exact metrics compared (current MRR and growth), and the batch shape (2 to 5 side by side). This clearly separates it from the single-record sibling get_startup, though no sibling is named explicitly.

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: an agent can infer this is the tool for head-to-head comparison of a small set of startups rather than a list search. There is no explicit statement of when not to use it or which sibling to prefer for single-entity lookups or broader discovery.

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