Skip to main content
Glama

ShowMRR

Get startup revenue

get_startup
Read-onlyIdempotent

Get one startup's public ShowMRR profile: current MRR, growth, verification status and source of the figure, and links.

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": "get_startup"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesShowMRR startup slug: the last part of a startup page address on showmrr.com, lowercase letters, digits and hyphens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the data is 'public' (no auth implied) and it discloses which fields the figure carries, including its verification status and source. Return format details and pagination or error behavior are absent.

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 sentence with the resource and the returned fields front-loaded after the colon. No redundant phrasing and nothing that could be cut.

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?

A one-parameter read tool with rich annotations and no output schema; the description compensates for the missing output schema by enumerating the returned fields. Only minor gaps remain, such as error behavior for an unknown slug.

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?

Only one parameter, fully documented in the schema at 100% coverage including regex pattern and the meaning of a slug. The description adds nothing about the slug, so the schema carries the semantics; baseline 3 applies.

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 and resource ('Get one startup's public ShowMRR profile') and enumerates the content returned: current MRR, growth, verification status, source, and links. The singular 'one startup' implicitly separates it from leaderboard, comparison, and history siblings, 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 single-startup lookup by slug. There is no explicit when-to-use, no exclusion such as 'use get_mrr_history for time series', and no prerequisite or failure-mode guidance.

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