Skip to main content
Glama

Little Works

export_outcomes

Export certified outcome records for training/eval (API key when LITTLEWORKS_MCP_API_KEY is set).

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_outcomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
placeNo
tradeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
minCertLevelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden; it does add genuinely useful behavioral context by disclosing the conditional API-key requirement tied to LITTLEWORKS_MCP_API_KEY. However it says nothing about what the export produces (file vs. inline records), volume/size behavior, or read-only safety, leaving the operation's effects underspecified.

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?

One compact sentence with the action and resource front-loaded and the auth caveat in a parenthetical. Nothing is wasted, though the parenthetical could have been spent on the undocumented filters instead.

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?

For a five-parameter export tool with no output schema and 80% of parameters undocumented, a single sentence is not sufficient. An agent cannot tell what the filters do, what the export returns, or how results are bounded by limit.

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

Parameters2/5

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

Schema coverage is only 20% across five parameters, and the description explains none of limit, place, trade, or minCertLevel. The single point it makes (apiKey required when the env var is set) restates the schema's own description, so it adds almost no meaning beyond the schema.

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 ('Export') and resource ('certified outcome records') plus the intended downstream use ('training/eval'). It does not explicitly contrast itself with the sibling query_outcomes or export_outcome_schema, so differentiation is only implicit.

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?

The phrase 'for training/eval' implies the context in which to reach for this tool, but there is no explicit when-not guidance and no named alternative for plain inspection of outcomes (e.g., query_outcomes). Usage is suggested rather than directed.

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