Skip to main content
Glama
io.github.sionjang101-create/taskattest

io.github.sionjang101-create/taskattest

Describe the spec format

describe_checks
Read-onlyIdempotent

Lists available check types, explains what each verifies, and supplies record-reconciliation and JSON-plus-report spec templates to use before writing task definitions.

Instructions

List the check types this server can run, what each one verifies, and two spec templates: a record reconciliation and a JSON-plus-report deliverable. Call this before writing a task definition.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
check_typesYes
tool_versionYes
spec_templateYes
verdict_rulesYes
spec_template_deliverableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds useful behavioral context by disclosing what the output contains (check types, verification semantics, two template shapes), which is more than the annotations provide.

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, no filler, with the primary purpose front-loaded and the workflow instruction placed last as the call to action. Every clause carries information the agent needs.

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?

For a zero-parameter read-only listing tool with an output schema present, this is nearly complete: purpose, returned content, and call timing are all stated. Minor gap: it does not explicitly connect its output to the follow-on tools (draft_spec, verify_task), though the "before writing a task definition" clause implies the handoff.

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 no parameters, so there is nothing to disambiguate and the baseline applies. The description correctly spends no words on parameter semantics.

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 and resource ("List the check types this server can run") and enumerates the returned content: what each check verifies plus two named spec templates. This clearly distinguishes it as a discovery/introspection tool rather than a drafting or execution tool.

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?

Gives explicit sequencing guidance: "Call this before writing a task definition," which tells the agent exactly where this fits in the workflow. It stops short of naming a specific alternative such as draft_spec or stating when it can be skipped, 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.