Skip to main content
Glama

Little Works

query_outcomes

Query certified outcomes: named problem → before/after state transition, filterable by trade, place, certLevel. Enterprise annotation index.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
placeNoe.g. victoria-bc
tradeNoe.g. siding, plumbing
minCertLevelNo0 listed … 2 transition … 5 settled
requireBeforeAfterNoDefault true — prefer definable state transitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Query' weakly implies a read, but nothing states permission requirements, result volume, pagination/limit behavior, or what 'certified' means operationally. 'Enterprise annotation index' adds no actionable behavior.

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?

Two short sentences, front-loaded with the resource and core concept; nothing is padded. The only waste is the trailing 'Enterprise annotation index' fragment, which occupies space without conveying usable information.

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 five-parameter read tool with no annotations and no output schema, the description covers the conceptual model and filters but leaves the return shape, default result size, and result ordering opaque. Adequate to attempt a call, not enough to predict its output.

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

Parameters3/5

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

Schema description coverage is 80%, so the schema already documents place, trade, minCertLevel and requireBeforeAfter; baseline is 3. The description usefully echoes trade/place/certLevel but adds no format or semantic detail beyond the schema (the certLevel scale 0–5 lives only in the schema), and omits the limit parameter entirely.

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 gives a specific verb and resource ('Query certified outcomes') and pins the domain model as 'named problem → before/after state transition', which is far more informative than the bare name. The closing phrase 'Enterprise annotation index' is unexplained jargon that muddies rather than sharpens the purpose, and no sibling (get_outcome, export_outcomes) is named for contrast.

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?

The filter list ('filterable by trade, place, certLevel') hints at usage but there is no when-to-use statement, no when-not, and no pointer to the singular get_outcome or the export_outcomes sibling. An agent must infer the retrieval-vs-export boundary entirely on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources