perseus

perseus_get_context

Read-only

Retrieve the full rendered Perseus context for the current workspace. Use to obtain an aggregated view of workspace state including git status, service health, and memory federation.

Instructions

Return the full rendered Perseus context for the workspace.

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

Input Schema

Name	Required	Description	Default
`format`	No	Output format: markdown or json (default: markdown)

Output Schema

Name	Required	Description	Default
`format`	No	Output format used
`rendered`	No	Full rendered context

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.7Jun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "format": {
+      "description": "Output format used",
+      "type": "string"
+    },
+    "rendered": {
+      "description": "Full rendered context",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Description is consistent with readOnlyHint annotation, indicating no mutation. It adds 'full rendered' to suggest completeness but does not disclose other behavioral traits such as response size or workspace scope restrictions.

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?

Single sentence, no wasted words. Front-loaded with action and object. Highly concise.

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

Completeness5/5

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

For a simple tool with one optional parameter and an output schema, the description fully covers its purpose and behavior. No missing details given the constraints.

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

Parameters3/5

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

Schema has 100% coverage for the single parameter 'format', including a description of values. Description adds no additional meaning beyond the schema, meeting baseline for high coverage.

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?

Description clearly states verb 'Return', resource 'full rendered Perseus context', and scope 'for the workspace'. It distinguishes from siblings by specifying 'context' specifically, which is unique among the sibling tools.

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?

No guidance on when to use this tool versus alternatives like perseus_read or perseus_list. No 'when not to use' or context for selection among similar tools.

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