Skip to main content
Glama

ShowMRR

Search startups

search_startups
Read-onlyIdempotent

Search ShowMRR startups by name or keyword. Returns each match with its current MRR, whether that MRR is verified or self-reported, and a link to its public ShowMRR page.

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": {
      "query": "<query>"
    },
    "name": "search_startups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesStartup name or keyword, e.g. "analytics".
categoryNoCategory name, e.g. "saas" or "ai".
verified_onlyNoOnly startups whose MRR is verified from a connected payment provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category name, e.g. \"saas\" or \"ai\". Use list_categories to see the categories that exist."New value: +"Category name, e.g. \"saas\" or \"ai\"."
  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 read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description still adds real value by disclosing the return payload (MRR value, verified vs self-reported provenance, public page link) for a tool with no output schema. It omits truncation/limit behavior and how matching is performed (substring vs fuzzy), which would have earned 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?

Two sentences, zero waste, with the core action front-loaded and the return shape second. Every clause earns its place.

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 4-parameter read tool with no output schema, the description covers both input intent and return contents, which is the main burden. Missing details are secondary: whether results are ranked, what an empty result looks like, and the effect of the limit cap.

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 coverage is 75%, with query, category and verified_only documented; only limit is undocumented. The description echoes the query semantics ("name or keyword") and ties "verified or self-reported" to verified_only, but says nothing about category filtering or result-count limits beyond what the schema already states.

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 ("Search ShowMRR startups by name or keyword") plus what a match contains. It is clearly a keyword-discovery tool, but never names the sibling that fetches a known startup by id (get_startup), so differentiation relies on inference.

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: searching by name or keyword suggests discovery when the exact startup is unknown. There are no explicit when-to-use or when-not-to-use statements, and none of the siblings (get_startup, compare_startups, get_leaderboard) are referenced as alternatives.

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