Skip to main content
Glama

Taipei Ledger

Company profile

get_company
Read-onlyIdempotent

One company's profile: English and Chinese names, industry, founded and listed dates, website, an English description written from cited company sources, its latest monthly revenue with growth measures, its five most recent filings, and how many supply-chain, Japan and investment records exist.

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

Input Schema

NameRequiredDescriptionDefault
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered; the description adds real value by disclosing the return payload in detail, which matters because there is no output schema. It does not say what happens when the company is unknown or how identifiers resolve.

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?

placeholder

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly, including revenue growth measures and record counts. The remaining gap is the input parameter format and the not-found behavior.

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

Parameters2/5

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

There is a single required parameter, 'company', with 0% schema description coverage, and the description never clarifies whether it is a name, ticker, or internal ID. This is the one place the description needed to compensate for the bare schema and it does not.

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 resource and enumerates its scope: names in two languages, industry, dates, revenue, five most recent filings, and record counts. It clearly reads as a single-company lookup, though it never names the sibling find_company as the tool for locating a company in the first place.

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 phrase "One company's profile" implies usage but never states when to prefer this over find_company for company discovery. There are no explicit exclusions or prerequisites such as requiring a resolved company identifier.

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