Skip to main content
Glama

Look up a firm in the markets directory

lookup_firm
Read-onlyIdempotent

A firm in Frontier Desk's markets directory, by name: what kind of firm it is in plain words, its own site, the relationships held for it (what it bought, backed, lent to or borrowed from, each naming the other party), and a line on its recent activity. Up to eight firms per call. This is the public projection: no internal ids, codes, tags, evidence text or third-party scores cross it, and no client, mandate or engagement is reachable here.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPart of a firm's name, for example "Monroe" or "CORE Industrial".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, closed-world), and the definition adds real context beyond them: a cap of up to eight firms per call and an explicit statement of what the public projection withholds (internal ids, codes, tags, evidence text, third-party scores). What it does not disclose is behavior on no-match or on many partial matches beyond the eight-firm cap.

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?

The definition is two sentences, with the return profile first and the projection boundary second, so the key framing is front-loaded and nothing is repeated from the title or schema. The field list is dense but each clause carries distinct information, though the first sentence is a long run of clauses.

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?

The definition is complete for a one-parameter read tool lacking an output schema, since it fully documents the returned fields and the disclosure boundary while annotations supply the safety profile. The remaining gap is how ambiguous or empty matches behave, which an agent would need to know before relying on the eight-firm cap.

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 a single parameter at 100% schema coverage the baseline is 3, and the definition earns more by making the matching semantics concrete: a name lookup where a partial name ("Monroe", "CORE Industrial") is enough, plus what the returned record contains. That tells an agent how to formulate the query rather than just naming the field.

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 definition states exactly what the tool returns for a firm found by name: firm type in plain words, its own site, the relationships held (bought, backed, lent to, borrowed from, each with the counterparty named), and a line on recent activity. Because no output schema exists, this enumerated return profile is the main way an agent learns what it gets, and the definition also distinguishes itself from internal-data siblings by declaring the public projection boundary.

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?

The query is implicitly a name-based lookup and the boundary clause ("no client, mandate or engagement is reachable here") rules out using it for client or mandate questions. However, no sibling is named and there is no explicit guidance on when to use it versus tools like list_markets or get_public_page, so routing must be inferred.

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