Skip to main content
Glama

AI Buildout Permits

Company Exposure

company_exposure
Read-onlyIdempotent

Every data-center project in the ledger that resolves to one ticker or company, in any role (tenant, operator, owner, permittee, equipment maker): status, place, first record date, first-seen date, stated on-site MW, plus counts by role, state and first-record year, and the link methods used. Requires a subscription.

Example questions:

  • "Which data-center projects resolve to ORCL, and since when?"

  • "How many Texas certifications name Amazon by year?"

  • "Where does Anthropic show up as a tenant?"

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
ticker_or_companyYesA ticker (AMZN, CRWV, 9432.T) or a company name (Anthropic, Vantage).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds two things beyond that: the 'Requires a subscription' access constraint and an explicit inventory of what is returned (status, place, first record date, first-seen date, stated on-site MW, plus role/state/year counts and link methods). It says nothing about pagination limits or result-set size, which matters for a 300-record 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?

Purpose is front-loaded in the first sentence, with the return inventory immediately after and the eligibility constraint last. The example-question block earns its space by aiding selection, though the opening sentence is a dense run-on that could be split for scanability.

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?

No output schema exists, so the description carries the return contract, and it does so by enumerating the per-project fields and the aggregate counts. Gaps remain around pagination behavior (whether more pages exist, how offset interacts with limit) and how unmatched or ambiguous company names are handled, but these are secondary for a read-only lookup tool.

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 only 33%: ticker_or_company is documented in the schema with format examples (AMZN, CRWV, 9432.T), but limit and offset have no descriptions anywhere. The description's phrase 'resolves to one ticker or company' reinforces the matching semantics but never explains pagination or what the limit bound of 300 implies. Below the 80% baseline, the description does not compensate for the undocumented pagination parameters.

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?

The description states a precise verb-and-resource: it returns every data-center project in the ledger that resolves to one ticker or company, enumerating the roles (tenant, operator, owner, permittee, equipment maker) and the fields returned. That scope ('resolves to one ticker or company, in any role') implicitly separates it from a generic project search like find_projects, but no sibling is named or explicitly contrasted.

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?

The three example questions ('Which data-center projects resolve to ORCL, and since when?', 'How many Texas certifications name Amazon by year?', 'Where does Anthropic show up as a tenant?') do real work here, showing the agent the exact shape of query this tool answers. There are no when-not-to-use conditions or named alternatives, so it stops at clear context rather than full routing guidance.

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.