macp-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_session

Read-onlyIdempotent

Read a MACP session's runtime history to view participants, proposals, evaluations, votes, and the winner, including every participant's messages.

Instructions

Show a session's state, participants, proposals, evaluations, votes and winner.

Reads the runtime's session history, so it includes every participant's messages.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	The MACP session id (from start_session).

Output Schema

Name	Required	Description	Default
`you`	Yes
`mode`	Yes
`phase`	Yes
`state`	Yes
`votes`	Yes
`history`	Yes
`committed`	Yes
`initiator`	Yes
`proposals`	Yes
`objections`	Yes
`session_id`	Yes
`evaluations`	Yes
`mode_version`	Yes
`participants`	Yes
`approve_totals`	Yes
`policy_version`	Yes
`majority_winner`	Yes
`blocking_objection`	Yes
`expires_at_unix_ms`	Yes
`started_at_unix_ms`	Yes
`configuration_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds one genuinely useful behavioral note — it reads full runtime history so every participant's messages are included, implying a potentially large, unfiltered payload — but says nothing about size, latency, or error behavior for an unknown session id.

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?

Two short sentences with no filler; the returned-content list comes first and the scoping caveat second. Every clause carries information.

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 one parameter, an output schema, and full annotations, the description only needs to state scope, which it does. The minor remaining gap is the absence of any guidance on when to prefer get_commitment or other siblings over a full session dump.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that session_id comes from start_session. The description adds no further parameter meaning, so the baseline of 3 applies.

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 uses a specific verb ('Show') and resource ('a session's state') and enumerates exactly what is returned: participants, proposals, evaluations, votes, winner. It is clearly distinguishable from start_session or get_commitment by resource, though no sibling is named 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?

Usage is only implied — an agent can infer this is the inspection tool for an existing session, but there is no explicit 'use this when...' or 'use X instead when...' and no mention of prerequisites such as needing a valid session_id from start_session.

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

Deploy Server