Skip to main content
Glama

Taipei Ledger

Data freshness

data_status
Read-onlyIdempotent

What this server holds and how fresh it is: when the data was built, the latest revenue month, row counts, and the valid values for industry, filing category, asset type, supply relation, Japan relation and GPU model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered and the bar is lower. The description still adds real value beyond them by disclosing the exact payload (build date, latest revenue month, row counts, enumeration domains), which is the behavioral detail an agent needs since no output schema exists. It stops short of stating whether counts are exact, approximate, or paginated.

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

Conciseness5/5

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

One sentence, front-loaded with the summary clause before the colon, then a tight enumeration of the returned fields. No filler, no restatement of the tool name or title, and the most important element (what data exists and how fresh) leads.

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 zero-parameter metadata tool with no output schema, the description carries the burden of describing return content and does so field by field. What is missing is minor: no indication of output shape/format, and no statement of how 'fresh' is measured beyond 'when the data was built' and 'latest revenue month'.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a no-arg tool applies. The sentence is spent entirely on output content rather than wasting space on absent inputs.

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 uses a clear framing ('What this server holds and how fresh it is') and then enumerates the concrete contents: build time, latest revenue month, row counts, and the valid values for six named dimensions. This tells an agent precisely what the tool surfaces, though it never names a sibling tool or explicitly frames this as the discovery/coverage tool relative to the search and lookup tools.

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?

Usage is only implied: by advertising 'the valid values for industry, filing category, asset type...' it hints that an agent should call this before filtering in tools like search_filings or screen_revenue, and 'how fresh it is' hints at checking staleness before trusting revenue results. There is no explicit when-to-use statement, no ordering recommendation, and no stated exclusions.

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