Skip to main content
Glama

Coordination state check

wever_coordination-state-check
Read-only

Agent Coordination: submit how a group of agents shares state: each shared record (a board, a file, a database, a document, a message thread, one agent’s own context or other) with its id, its name, its owner, the agents that write it and read it, the rule that settles two writes (one writer only, a lock, a versioned merge, the owner decides, the last write wins or no rule), what it keeps (a full change log, snapshots, the latest value only or nothing) and where a joining agent finds it; and optionally the agents in the group. The signed report lists every record with its writers, rule, history and whether a joining agent can rebuild it, counts the records with several, one or no writers and each rule, and names shared state that is unsafe: records with no named owner or writer, records several agents can overwrite with no conflict rule, and state a joining agent cannot reconstruct because it lives in one agent’s context, keeps nothing or has no location; then writers with no owner, last write wins, latest-value-only history and writers outside the group, with the fix for each. One agent’s view against the system record after an interruption is wever_state-reconciliation-check and partly done work in one task system is wever_partial-state-check. Verdict shared_state_unsafe, shared_state_gaps, shared_state_unverified or shared_state_sound. POST /api/coordination-state-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-coordination-contract. Human page: https://weverlabs.com/agent-coordination/.

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": {
      "records": "<records>"
    },
    "name": "wever_coordination-state-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional name recorded in the report.
agentsNoThe agents in the group, to read writers against.
recordsYesEach shared record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses payment terms, x402 exact settlement, free-call limits, required wallet proof binding, endpoint, signed Ed25519 receipt, and that it performs no network fetch, message, sharing, configuration change, money movement, or external write. This gives an agent the operational and safety context needed before invocation.

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?

The description is front-loaded with purpose and report behavior, and most content is relevant. However, it uses very long semicolon-chained sentences and repeats many enum meanings already present in the schema, making it denser and less scannable than necessary.

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 complex no-output-schema tool, the description explains the input shape, report contents, unsafe-state categories, verdict values, endpoint, auth/payment requirements, and receipt signing. It also states the read-only external-effect boundary, leaving little ambiguity about what a caller gets back.

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 description largely restates what the schema already documents: record id, kind, name, owner, readers, writers, write_rule, history, location, and optional agents. It integrates those fields into the coordination-state concept, but adds little field-level meaning beyond the already rich 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?

The description states a specific resource and operation: submitting a group's shared-state model for a signed coordination-state check, then enumerates the report contents and verdicts. It explicitly distinguishes this from wever_state-reconciliation-check and wever_partial-state-check, so an agent can identify its role without opening sibling schemas.

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 description supplies clear context for when this tool applies: group shared-state records, unsafe ownership/write-rule/history/location gaps, and writers outside the group. It names two alternative checks and what they cover, but does not give an explicit 'use this instead when...' rule or exclusions for the other coordination siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources