Skip to main content
Glama
coss-mcp

coss-mcp

Official
by cosscom

Search the coss.com docs

search_docs
Read-only

Search coss.com documentation across guides, SDK pages and API reference to find matching pages with relevant passages. Use it to locate answers, then read full pages with read_docs.

Instructions

Searches coss.com's documentation (guides, SDK pages and the API reference) and returns the matching pages with the passages that matched. Read a page in full with read_docs. 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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pages to return.
queryYesWhat to look for, e.g. "verify webhook signature" or "schedule an email".

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 safe read (readOnlyHint=true, openWorldHint=false), so the description is not carrying the safety burden. It still adds useful context beyond the annotations: results are page-level with matching passages, and no API key is required. It does not mention rate limits or result variability, which keeps it below a 5.

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?

Three short sentences with no wasted wording: purpose and return shape are front-loaded, the alternative follows, and the auth note closes. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage and annotations covering safety, what remains to disclose is the return shape and the handoff to read_docs, both of which are present. No output schema exists, but the description explains the response in one clause.

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

Parameters3/5

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

Schema description coverage is 100%, with both query and limit documented in the schema, including examples and bounds. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (searches) plus the exact resource and its scope (coss.com documentation: guides, SDK pages, API reference), and describes the return shape (matching pages with matched passages). This clearly distinguishes it from read_docs, which retrieves full pages.

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?

Explicitly routes the agent to read_docs when a full page is needed, establishing the search-then-read workflow. It also notes the tool works without an API key, removing an auth prerequisite. It stops short of saying when not to search or how to craft queries, so it is clear but not exhaustive.

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