Skip to main content
Glama
Sign In
Decision State MCP

Decision State MCP

by Koolercat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Task Context

get_task_context

Retrieve compact decision-relevant state for a task, including goals, constraints, facts, and decisions.

Instructions

Return compact decision-relevant state for a specific task.

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": {
      "task": "<task>"
    },
    "name": "get_task_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Without annotations, the description bears full responsibility for disclosing behavior. It implies read-only access via 'return' but does not confirm safety, error handling, or what constitutes 'compact' state. Critical traits like idempotency or side effects are omitted.

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?

The description is a single, well-formed sentence. It is concise but arguably too brief—adding one more sentence about parameters or return format would improve informativeness without sacrificing brevity.

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?

Given the lack of annotations, output schema, and parameter descriptions, the tool is incompletely specified. A simple two-parameter retrieval tool should document parameter roles and return value nature to ensure correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to the parameters 'task' or 'limit'. The agent cannot infer what 'task' qualifies as an identifier or how 'limit' affects the result (e.g., max number of items).

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 clearly states the tool returns 'compact decision-relevant state for a specific task,' which indicates a focused retrieval operation. It distinguishes from siblings like 'get_session' and 'get_state' by specifying task-specific scope, but does not explicitly contrast them.

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 description provides no guidance on when to use this tool versus alternatives like 'get_session' or 'get_state'. There is no mention of preconditions, scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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