Skip to main content
Glama
IEZhu

Agents-Core

by IEZhu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read cooperation state

cooperation_read
Read-only

Read a repository's cooperation snapshot and events to track shared state and activity. Use it after resuming or when a stale revision invalidates the cursor, then restart with a new snapshot.

Instructions

Read one authorized repository's consistent cooperation snapshot and events.

Read again after resuming or a stale revision; cursor_expired requires a new
snapshot. Artifact references grant no file access and are never fetched.
Request and response schemas: agents-core://cooperation/schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesClosed agents-core/cooperation/1 read object or raw JSON. Required protocol and repository_id; optional cursor (event cursor integer), limit (1..100, default 50), offset (snapshot pagination integer >=0, default 0), snapshot_time (nonnegative timestamp), participant_ids, agreement_ids, task_ids (each at most 50 IDs). Follow next_snapshot_offset and repeat the first page's snapshot_time; restart snapshot pagination if revision or service_epoch changes. Follow next_cursor for events. No capability is returned. Maximum 32768 UTF-8 bytes, depth 8; no unknown fields or duplicate keys.
workspaceNoAbsolute path of your working directory, the project this session works in. Pass it whenever you have one: one server can serve several sessions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv26.10.16

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint=false annotations, it discloses consistency semantics ('consistent cooperation snapshot'), staleness/refresh behavior ('read again after resuming or a stale revision; cursor_expired requires a new snapshot'), and an important security boundary ('artifact references grant no file access and are never fetched'). This is well past what the annotations convey.

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?

Three short sentences, front-loaded with what is read and followed by operational caveats and a pointer to the canonical schema URI. No filler, though the phrasing is terse enough that some clauses need a second read.

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?

With an output schema present, a fully documented request object, and annotations covering the safety profile, the remaining burden on the description is behavioral policy — consistency, staleness, pagination restart cues, and the artifact-access caveat — all of which are supplied. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the request object already documents cursor, limit, offset, snapshot_time, ID filters, and error/revision handling in detail. The description adds only peripheral semantics (cursor_expired, artifact references), which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb and resource: 'Read one authorized repository's consistent cooperation snapshot and events.' Scope ('one authorized repository') and returned content types (snapshot, events) are explicit, so the agent can distinguish it from cooperation_apply/send/ack 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 Guidelines4/5

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

It gives concrete usage conditions: re-read after resuming or a stale revision, and that cursor_expired requires a new snapshot. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is clear context without full routing guidance.

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