harness-manager

Overview Schema Source Related Servers Discussions Admin

card_describe

Read-only

Retrieve enablement and sharing baselines for Skill, Rule, or Hook cards, including project-local composite user, shared project, and personal overrides.

Instructions

读取 Skill, 规则或 Hook 卡片的启用与共享基线. project-local 合成用户, 共享项目和个人覆盖.

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": {
      "id": "<id>"
    },
    "name": "card_describe"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`scope`	No		user

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict this. It adds some context about scope composition ('project-local 合成用户, 共享项目和个人覆盖'), but the wording is cryptic and adds limited actionable behavioral detail beyond the annotation.

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?

The description is compact and the main verb-resource pair is front-loaded. The second clause is grammatically awkward, but there is no redundant filler or repetition of schema fields.

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

Completeness2/5

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

Despite having an output schema and read-only annotation, the description leaves the meaning of 'composite user' and the exact role of scope unresolved, and it gives no guidance on what values id/scope take. This is not enough for an agent to invoke the tool reliably.

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%, so the description needed to explain id and scope. It never names id, and scope is only obliquely hinted at through the phrase about project-local, shared project, and personal overrides. This is insufficient to compensate for the empty schema descriptions.

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 states a clear verb ('读取' / read) and a specific resource: the enablement and sharing baseline of Skill, Rule, or Hook cards. This distinguishes it from mutation siblings like card_configure and card_set_shared, though the trailing phrase 'project-local 合成用户...' weakens clarity.

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

Usage Guidelines3/5

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

The read verb implies the tool is for inspecting baseline settings rather than modifying them, but it never explicitly says when to prefer this over card_configure or card_set_shared, nor does it state exclusions or prerequisites.

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