Skip to main content
Glama
Sign In
Mirsad

Mirsad

by amkkoussay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

record_outcome

Attach a later outcome or result to an existing decision so agents can record what happened and keep shared memory accurate.

Instructions

Attach a later outcome/result to an existing decision.

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": {
      "decision_id": "<decision_id>",
      "outcome": "<outcome>",
      "agent": "<agent>"
    },
    "name": "record_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
outcomeYes
decision_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 entire burden and does almost none of it. It does not say whether the outcome is appended or overwrites a previous one, whether multiple outcomes per decision are allowed, what error occurs for an unknown decision_id, or what permissions are needed.

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 front-loaded sentence with no wasted words. Its brevity is efficient rather than padded, though it borders on under-specification given the tool's mutation semantics.

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 three-parameter mutation tool with no annotations, no output schema, and zero schema coverage, the description is too thin. An agent cannot tell what the call returns, how failures are reported, or what 'agent' is meant to contain.

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 description coverage is 0% across three required parameters, so the schema gives only bare titles. The description implicitly maps 'outcome' and 'decision_id' but says nothing about the third parameter, 'agent' (who or what is recording the outcome), nor about expected formats or value constraints.

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+resource: attaching a later outcome/result to an existing decision. That distinguishes it from record_decision, which creates the decision in the first place, though the description never names that sibling explicitly.

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 'later outcome' implies the timing of use, i.e. after a decision has been made and its results are known, but there is no explicit when-to-use rule, no exclusion against recording a new decision, and no prerequisite such as the decision_id needing to exist.

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

Deploy Server

Other Tools