Kosmodrom

task_context

Read-only

Returns a task or bug by ID or number (unique within the company): spec, gist (gistInfo.stale - the spec changed after the gist), category, type (severity for bugs; bugType - defect nature), feature (feature.spec with includeFeatureSpec; the full feature plan is in the feature context), relations (dependencies - what it waits for; blockedTasks - what waits for it), allowedActions, specRevision, productID and a page of the task chat. Imported designs are in designs (design: markers; snapshotFID, contextFID with contextSize, assetsFID) the design block holds design files and the main frames of the task's modules (for visual work), and attachments are in attaches by fid; raw design links without a designs entry are not imported. Useful when the user mentions a task number or asks about a task.

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

Input Schema

Name	Required	Description
`ID`	No	Task ID; preferred over key.
`key`	No	Task number without a prefix, e.g. 25865, if the ID is unknown.
`chatAfter`	No	Read messages newer than chat.after.
`chatLimit`	No	Chat messages to return (default 20, max 100).
`chatBefore`	No	Read messages older than chat.before.
`includeFeatureSpec`	No	true includes the full feature spec (feature.spec); omitted by default.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- changedInput schema / properties / chatLimit / maximum
```
Previous value: -9007199254740991New value: +100
```
- changedInput schema / properties / chatLimit / minimum
```
Previous value: --9007199254740991New value: +1
```
- removedInput schema / properties / key / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / key / minimum
```
Removed value: --9007199254740991
```
First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description goes well beyond that, disclosing rich return behavior: gist staleness signaling, dependency/blocked relations, allowedActions, design import rules ('raw design links without a designs entry are not imported'), and a paginated chat slice. This is substantial added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense run-on sentence stuffed with nested parentheticals (gist, relations, design markers, fids), which is hard to parse despite being front-loaded with the core purpose. It could be restructured into a short purpose line plus a return-fields block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-shape burden, and it does extensively, enumerating the fields a caller will get. This is thorough for a read tool; minor gaps remain around pagination defaults already handled in schema.

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. The description adds value by linking includeFeatureSpec to feature.spec and noting the ID-vs-number preference, tying parameters to visible outcomes rather than merely restating the schema.

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

Purpose5/5

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

States a specific verb and resource ('Returns a task or bug by ID or number'), and the ID-vs-number lookup distinguishes it from search-oriented siblings like task_search. An agent can identify it immediately without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing line gives clear usage context: 'Useful when the user mentions a task number or asks about a task.' This establishes trigger conditions but does not name an explicit alternative (e.g., task_search) or state when not to use it.

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

All Kosmodrom tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?