Skip to main content
Glama
Sign In
Skills MCP Server

Skills MCP Server

by Blindex09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

a11y_trace

Retrieve the ordered session trace of every action, reach, and probe with returned facts, providing the step numbers that a11y_finding cites as evidence.

Instructions

The ordered trace of this session (every action, reach and probe with the facts it returned). The step numbers here are the evidence a11y_finding cites.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral weight. It discloses the content shape (every action, reach and probe with the facts it returned), which implies a read-only, session-scoped retrieval, but says nothing about size, ordering guarantees, or whether the trace is complete or truncated.

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?

Two sentences, both front-loaded with the essential information, and the second sentence ties the tool to its consumer. No waste.

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?

An output schema exists, so the description need not explain return values; it nonetheless characterizes the trace's contents. For a zero-parameter read tool this is nearly complete, with only trace size/ordering left unspecified.

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?

The tool takes zero parameters, so there are no parameter semantics to document; the baseline for a 0-param tool applies. No misleading claims about inputs are made.

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 resource — the ordered trace of the session — and enumerates its contents (actions, reaches, probes with returned facts). It does not name a verb, but 'trace of this session' is unambiguous and clearly distinct from siblings like a11y_finding or a11y_probe.

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?

Usage is implied through the cross-reference to a11y_finding ('the step numbers here are the evidence a11y_finding cites'), which suggests reading the trace to verify findings. There is no explicit when-to-use or when-not-to-use, nor are alternative retrieval tools named.

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