Skip to main content
Glama
Sign In

Traceable

by com.traceabledocs.app
OverviewDiscussionsAdmin

Read a skill

traceable_skill_read
Read-onlyIdempotent

One skill as a SKILL.md file: YAML front-matter (name, description, and Traceable metadata: title, tags, status, version and source document) followed by the instructions in Markdown. Serves the skill as it stands in its document's latest published version; status "draft" serves the open draft instead, which is not yet official, and is refused where your organisation allows agents published skills only. In an organisation under controlled releases this works once an admin turns on Agents read skills.

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": {
      "skillId": "<skillId>"
    },
    "name": "traceable_skill_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNopublished (default) or draft
skillIdYesA skillId from traceable_skill_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses which version is served (latest published of the source document), the semantics and official status of drafts, the policy-based refusal case, and an org-level feature-flag gate. These are exactly the behavioural facts an agent cannot get from annotations or 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?

Three sentences, front-loaded with the return format, followed by version/status behaviour and the permission gate. Dense and largely waste-free, though the middle sentence carries several clauses and could be split for readability.

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?

No output schema exists, and the description compensates by describing the returned document's structure and front-matter fields, plus the version and permission conditions. Missing only secondary details such as not-found/error behaviour or whether the returned file is ever truncated.

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 baseline is 3; the description earns more by explaining what 'draft' actually means (open draft, not official, refused under published-only policy) and that the served version is derived from the source document's latest publication. It does not restate skillId semantics, which the schema covers.

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?

States a specific verb and resource ('One skill as a SKILL.md file') and enumerates what the returned document contains (YAML front-matter fields plus Markdown instructions). It does not name the obvious sibling traceable_skill_list as the alternative source of IDs, so differentiation is implied rather than explicit.

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?

Explains when the draft path applies (status 'draft' serves the open, not-yet-official draft) and when it is refused (organisations restricting agents to published skills). It also flags the prerequisite that an admin must enable 'Agents read skills' under controlled releases. No explicit statement of when to call this instead of skill_list, hence not a 5.

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

All Traceable toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources