Skip to main content
Glama
Sign In
irkumo-mcp

irkumo-mcp

by ozumin-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_fields

Retrieve available data columns, unit credit costs, and source attribution for irkumo-mcp company and financial datasets. Use it to inspect field definitions before querying.

Instructions

利用可能な列の一覧と単価､データの出典情報を取得します (消費クレジット: 0)｡

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the operation's cost ('消費クレジット: 0', i.e. a free call) and describes what is returned, but it never states the read-only, side-effect-free nature of the operation explicitly.

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?

A single front-loaded sentence that names the resource first and appends the cost note. Every element earns its place with no redundancy.

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 listing tool with no output schema, the description adequately enumerates the returned content (columns, unit prices, source info). It is nearly complete, with only the return structure/shape left unspecified.

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 nothing for the schema or description to document; the baseline of 4 for a parameterless tool applies. No parameter semantics are needed or missing.

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 verb (取得します/retrieve) and concrete resources: available columns, unit prices, and data source information. The purpose is unambiguous, though it offers no explicit differentiation from the company-oriented siblings (search_companies, get_company).

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 – an agent can infer this is the discovery tool for learning what fields exist before searching, but the description never says when to reach for it versus the sibling company tools or what to do with the result. No exclusions or alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools