Skip to main content
Glama

Little Works

export_outcome_schema

JSON schema for Little Works certified outcomes — same records for enterprise query and training/eval.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 disclosure burden, and it delivers little: it does not confirm this is a read-only fetch, does not describe output shape or size, and does not say whether the schema is versioned or stable. The one piece of useful context is that the schema covers the same record set used by enterprise query and training/eval, but that is more provenance than 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?

A single short sentence with the subject (JSON schema for certified outcomes) front-loaded and no padding. The em-dash clause is terse to the point of ambiguity, but it does not waste words.

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?

With no annotations, no output schema, and no parameters, the description is the only signal available, and it leaves the core question unanswered: what exactly comes back and how it differs from export_outcomes. For a zero-argument utility tool a single sentence could suffice, but only if it resolved that ambiguity.

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 input schema declares zero properties, so there are no parameters whose meaning could be lost; the baseline for a no-parameter tool applies. The description adds nothing parameter-related, but there is nothing to add.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the artifact as a "JSON schema for Little Works certified outcomes," which is a recognizable resource, but it never states the action (retrieve/export) or the result format explicitly, so an agent must infer whether this returns a schema document, records, or a pointer. It also fails to distinguish itself from the near-identically named sibling export_outcomes, which is the most likely selection error.

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?

There is no when-to-use guidance, no mention of when not to use it, and no routing to export_outcomes for actual records. The trailing clause "same records for enterprise query and training/eval" gestures at context but reads as a remark about record provenance rather than a condition for invoking this tool.

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