Skip to main content
Glama
Sign In
microCMS Document MCP Server

microCMS Document MCP Server

Official
by microcmsio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fetch_general

Retrieves general documentation about microCMS, providing an overview and common information to answer questions.

Instructions

microCMSについての質問に答える場合、まずこのツールを利用します。docs/general.md の内容を返します。これにはmicroCMS全体の概要や共通情報が書かれています。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states that the tool returns the content of a specific markdown file, which is helpful. However, it does not disclose any potential side effects, rate limits, authentication needs, or error behavior. The transparency is adequate but could be improved.

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?

The description is concise, consisting of two short sentences in Japanese. It front-loads the purpose and provides immediate value without any extraneous information.

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?

Given the tool's simplicity (no parameters, no output schema), the description provides enough context: what the tool does and when to use it. It could be more explicit about the format of the returned content, but overall it is complete for its purpose.

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 has zero parameters, so the schema description coverage is effectively 100%. The description adds no parameter information, but with zero parameters, this is acceptable. Baseline for 0 params is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to answer questions about microCMS by returning the content of docs/general.md. It specifies the action (fetch) and resource (general.md), and implicitly distinguishes from siblings like list_documents and search_document.

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 description explicitly says 'first use this tool' when answering questions about microCMS, providing clear usage context. While it does not list alternatives or when-not-to-use, it implies that for general info this tool is primary, and siblings are for specific document listing/search.

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