Skip to main content
Glama
coss-mcp

coss-mcp

Official
by cosscom

Read a coss.com docs page

read_docs
Read-only

Fetches a coss.com documentation page as Markdown from a path or URL, such as a search_docs result; use offset to continue reading long pages.

Instructions

One page of coss.com's documentation as Markdown: a guide, an SDK page, or an API reference page (method and URL, parameters, request body, responses, errors and examples in each SDK). Takes a path from search_docs or a docs link, e.g. "/docs/email/sending" or "/docs/api-reference/emails/send-email"; "/docs" is the index of every section. Works without an API key.

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": {
      "page": "<page>"
    },
    "name": "read_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page's path or URL, e.g. "/docs/webhooks".
offsetNoCharacter to start from, for a page longer than one answer (`next_offset`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world operation, so the bar is lower, and the description still adds real context: the return format is Markdown, page contents include parameters/responses/errors, and it "works without an API key," which removes an auth concern an agent might otherwise worry about. Pagination is only implied via the offset parameter rather than explained here.

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?

It leads with what is returned and then packs the input format, examples, and auth note into a compact block with no filler. The single long colon-heavy sentence is dense but every clause carries 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?

For a two-parameter read tool with no output schema, the description covers content, format, input form, and auth, which is nearly everything needed to call it correctly. The only gap is how truncation is surfaced, which is left to the offset parameter's schema text.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by clarifying the accepted page form (path or docs link) and giving two contrasting examples plus the meaning of "/docs" as the index. The offset/truncation mechanics remain solely in the schema.

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 gives a specific verb and resource ("One page of coss.com's documentation as Markdown") and enumerates the page kinds it covers: guides, SDK pages, and API reference pages whose contents are spelled out. An agent can immediately tell this is a single-page fetch, distinct from the sibling search tool.

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?

It establishes the retrieval workflow by saying the path comes "from search_docs or a docs link," pointing to the sibling for discovery, and notes "/docs" is the index of every section, which gives a starting point. It stops short of stating when not to use it or what to do if a path is unknown.

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