Skip to main content
Glama

Little Works

get_outcome

Get one certified outcome by outcomeId or entityId (project id).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "outcomeId": "<outcomeId>"
    },
    "name": "get_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeIdYesoutcome_… id or project_… entity id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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. It implies a read-only single fetch and hints that a project id can resolve to an outcome, but says nothing about permissions, behavior when the id does not exist, or what 'certified' guarantees about the returned record.

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?

One short sentence, front-loaded with the verb and resource, followed by the acceptable id forms. Nothing is padded or repeated.

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 one-parameter, no-output-schema, no-annotation lookup this is close to sufficient, but it never explains what a 'certified outcome' contains or what happens on a miss, which the agent cannot learn elsewhere.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds non-obvious meaning: the single parameter accepts either an outcome id or an entity/project id, which the schema only gestures at. The parenthetical '(project id)' disambiguates what 'entityId' means.

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 (Get) and a specific resource (one certified outcome), and names the two identifier forms accepted. An agent can tell it is a single-item lookup rather than a list/export (e.g. export_outcomes). The term 'certified' is domain jargon left unexplained, so the object being fetched is not fully transparent.

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?

Implies usage: fetch exactly one outcome by id, and notes that a project/entity id can substitute for an outcome id. There is no explicit statement of when to prefer this over export_outcomes or a project-level tool, and no error/prerequisite guidance.

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