PerMark

get_context

Read-only

Retrieves current PerMark document, mode, section, selection, unsaved changes, and open comments so AI agents can align work with the user's review position.

Instructions

Where the person is in PerMark now: document, mode, section, selection, unsaved, open comments.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 23, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv0.1.0Oct 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's real contribution is enumerating what is returned (document, mode, section, selection, unsaved, open comments), which effectively substitutes for the absent output schema. It stops short of saying what happens when nothing is open or how facets are structured.

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?

A single compact clause listing the state facets with zero filler. The scope marker 'now' is front-loaded, so the key semantic (current, live state) lands immediately.

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?

With no parameters and annotations covering read-only safety, the only gap was the return contract, and the description fills that by listing the state facets. It is nearly complete; minor omissions are the shape of each facet (e.g. whether 'open comments' is a list) and the empty-state behavior.

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?

The tool takes zero parameters, so the baseline of 4 applies. There is no parameter behavior an agent could get wrong.

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 names a specific resource (the user's current position/state in PerMark) and even enumerates the facets: document, mode, section, selection, unsaved, open comments. That is far more than a tautology of 'get_context'. It does not, however, differentiate itself from siblings like 'read_note' or 'outline', so the agent must infer the boundary.

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 'Where the person is in PerMark now' implies a live-state lookup, so the use case is inferable. But there is no explicit when-to-use, no when-not-to-use, and no mention of alternatives such as 'read_note' or 'outline' for reading content rather than position.

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

Deploy Server