Skip to main content
Glama

功能覆盖清单

cocos_coverage
Read-only

Inspect coverage across all 54 Cocos modules, including acceptance scope, capabilities, service tool counts, and historical evidence; partial status does not mean operations are unavailable.

Instructions

查看全部 54 个模块的范围验收、能力与独立服务工具计数及历史证据;partial 不代表没有可用操作

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

Input Schema

NameRequiredDescriptionDefault
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / projectId
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the description need not restate it. What the description does add is genuinely useful interpretive context: the report spans 54 modules and includes historical evidence, and a 'partial' status does not imply the absence of usable operations. It still omits return shape and pagination/size characteristics, which matters given there is no output schema.

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?

One compact sentence plus a semicolon-joined caveat, with the verb and scope front-loaded. No filler or repetition. It could be tightened only slightly by making the 'partial' caveat its own scannable clause.

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

Completeness3/5

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

For a read-only reporting tool with no output schema, the description does convey what the report contains (acceptance status, capability counts, historical evidence) and warns about misreading 'partial'. However, it leaves the sole parameter unexplained and gives no sense of report size or format, which is a meaningful gap for a 54-module inventory.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional projectId parameter, so the schema supplies no meaning at all. The description never mentions projectId, whether it defaults to a connected project, or how scope changes when it is supplied. With low coverage the description is expected to compensate, and here it does not.

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?

The description names a specific verb ('查看' / view) and a concrete resource: a coverage inventory across all 54 modules covering scope acceptance, capabilities, standalone service tool counts, and historical evidence. That is clearly distinct from siblings like cocos_capability_search or cocos_workflow_status. It stops short of a 5 because the term '模块' (module) is never grounded, leaving the agent to infer what unit is being counted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The trailing clause 'partial 不代表没有可用操作' is a caveat about interpreting results, not a routing rule for choosing this tool. The agent can only infer usage from the noun phrase 'coverage list'.

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