Skip to main content
Glama

Look up a company's funding and size

getCompanyFunding
Read-onlyIdempotent

What Clera has on file about one company: its latest funding stage, last round date and amount, the total raised across rounds with a known amount, how many rounds are on file, and its headcount from LinkedIn. Triggers: "how much did the candidate's company raise", "what stage is Acme at", "how big is her current company", "is his last startup any good".

Pass the company name as it appears on the candidate's profile, plus its website domain or LinkedIn slug when you have one, which matches more reliably. It only reads what Clera already stores.

No funding on file means Clera does not have it, not that the company is unfunded. Say plainly that we don't have their funding, and never guess a number.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe company name as it appears on the candidate's profile.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
domainNoThe company's website domain, such as acme.com, when you have it.
linkedinSlugNoThe company's LinkedIn slug, the part after linkedin.com/company/, when you have it.

Output Schema

NameRequiredDescriptionDefault
foundYes
isPublicYes
roundCountYes
companyNameYes
latestStageYes
employeeCountYes
lastRoundDateYes
knownRaisedUsdYes
roundsWithAmountYes
lastRoundAmountUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/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, and the description stays consistent while adding real value: data provenance ("only reads what Clera already stores"), absence semantics (no funding on file means Clera lacks it, not that the company is unfunded), and a logging/privacy disclosure. It does not address ambiguous name matches or which record wins when domain and name conflict, which keeps it from the top score.

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?

It is front-loaded with the returned fields, then parameter guidance, then the null-handling rule, then the logging note — a sensible order. Four paragraphs is slightly long for a single lookup, and the quoted trigger list is somewhat redundant with the opening sentence, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, yet the description still frames them, and it covers the two failure modes an agent would otherwise get wrong: missing data (do not guess, say we don't have it) and identifier choice for reliable matching. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, and the description earns more by explaining a preference the schema does not: supplying domain or LinkedIn slug in addition to the profile name "matches more reliably". That is a matching-strategy hint an agent can act on, not a restatement of field docs.

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?

The description names a specific resource (one company) and enumerates exactly what it returns: latest funding stage, last round date and amount, total raised across rounds with known amounts, round count, and LinkedIn headcount. That level of specificity lets an agent distinguish this lookup from general profile tools such as readCompanyProfile without opening a schema.

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

Usage Guidelines4/5

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

Concrete triggers are quoted ("what stage is Acme at", "how big is her current company"), which makes the intended call context clear. It stops short of naming an alternative tool or stating when not to use it, so an agent must infer that broader company facts belong elsewhere.

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