Return table/column meanings and full-text search targets to guide accurate SQL and search queries. Use live=true to view the schema of refreshed data.
テーブル/列の意味・FTS 対象を返す。AI が SQL/検索の前に読む。
live=True で refresh_data 後の最新データ(live ストア)のスキーマを見る。
| Name | Required | Description | Default |
|---|---|---|---|
| live | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It explains what is returned and the live-store behavior, and the verbs '返す' and '見る' imply a read-only operation. However, it does not explicitly state whether the operation has side effects or what happens when live=True is used before refresh_data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and front-loaded: the first sentence states purpose and usage timing, the second clarifies the optional parameter. Every sentence earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-optional-parameter tool with an output schema present, the description covers purpose, timing, and the live parameter's relationship to refresh_data. Nothing critical is missing for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only provides a default for live with no description, so the description must add meaning. It explains that live=True shows the latest schema after refresh_data, which is essential parameter context. It does not explicitly define live=False, but the default and contrast are inferable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns table/column meanings and FTS targets, with a specific intended use: reading before SQL or search. This distinguishes it from sibling tools like run_sql and search_text, which execute queries rather than describe schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to read this before SQL/search operations, giving clear context for when it should be used. It also explains that live=True should be used after refresh_data to see the latest schema, but it does not explicitly state when not to use it or name alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.