Skip to main content
Glama

Get one business profile

get_business
Read-onlyIdempotent

Use when the user names one AI company or agent (e.g. Cursor, Lovable) and asks about its revenue, pricing model or growth. Returns one business's full sourced record. Example: {"slug":"cursor"} -> Cursor with every figure and its source. Use it when you already have the slug (from search_businesses or leaderboard); it is the fullest view: every dated revenue figure (label, value, as_of, source_url), what it does, model, tier, lessons, growth series, related businesses, and the verification_label ("reported, not payment-verified" unless processor-verified). Unknown slug -> isError. Cost: free (100 calls/day without a key).

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

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug, e.g. cursor, lovable (from search_businesses or leaderboard).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Business slug, e.g. cursor, lovable (from search_businesses or leaderboard)."
  2. Changed5 schema fields changed
    • addedOutput schema / properties / result / properties / referral
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / properties / signup_go_url
      Added value: +{
      +  "description": "Same link via mrrledger.com/go/<slug> (counts the click, then 302)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / signup_url
      Added value: +{
      +  "description": "Referral link (only on businesses with one). Always shown with signup_url_disclosure; never affects figures, ranking, sorting or verification.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / signup_url_disclosure
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / signup_url_label
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds genuinely new behavior: the isError outcome for unknown slugs, the rate-limit context ('100 calls/day without a key'), and the meaning of verification_label ('reported, not payment-verified'). That last point is a real interpretive disclosure rather than a restatement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger and example, then the return contents and cost. Slightly overlong: enumerating every returned field ('label, value, as_of, source_url', 'lessons, growth series, related businesses') duplicates the output schema and could be trimmed.

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-parameter read tool with an output schema, this is more than adequate: it covers trigger, prerequisite, error case, and cost. The only slack is the redundant field enumeration, which the output schema already provides.

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 100% and the slug parameter's description already explains its format and origin, so the schema does the heavy lifting. The worked example {"slug":"cursor"} is a small reinforcement but adds no syntax or constraints beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns one business's full sourced record') and immediately scopes it with the trigger 'user names one AI company or agent'. The phrase 'it is the fullest view' implicitly distinguishes it from leaderboard/search_businesses, which return partial views.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use trigger ('names one AI company and asks about its revenue, pricing model or growth') and names the prerequisite and source of the slug ('from search_businesses or leaderboard'). Failure mode is also stated: 'Unknown slug -> isError.'

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