Skip to main content
Glama

ShowMRR

Get MRR history

get_mrr_history
Read-onlyIdempotent

Daily MRR history of one startup. Each point says whether ShowMRR read it from a connected payment provider or it was self-reported.

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_mrr_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to go.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful context beyond that: each data point carries provenance indicating whether ShowMRR read it from a connected payment provider or it was self-reported, which tells the agent how to interpret data quality. It stops short of stating pagination or truncation behavior for long ranges.

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 short sentences, zero filler, with the core purpose front-loaded and the provenance caveat following. Nothing could be removed without losing information.

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?

With no output schema, the description does the important work of explaining what a returned point represents and how to read its source flag. For a simple two-parameter read tool with full schema coverage and strong annotations, that is close to sufficient; a brief note on what happens for days with no data would close the remaining gap.

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?

Schema description coverage is 100%, so both slug and days are fully documented in the schema, including the slug pattern and the 1–365 range. The description adds no additional meaning about either parameter, so the baseline of 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?

"Daily MRR history of one startup" states a specific verb (retrieve history), a specific resource (MRR), and the scope (a single startup). That distinguishes it from siblings like get_leaderboard or compare_startups, 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 by the scoping phrase "of one startup" – an agent can infer this is the per-startup time-series tool rather than a ranking or comparison tool. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_startup for current values only).

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