Skip to main content
Glama

Show a shared space's reconciliation policy

get_reconcile_policy
Read-only

Retrieve the source-aware reconciliation policy for a space to see how superseded facts and conflicts are handled, including the default RECENCY setting when no policy is configured.

Instructions

Show the source-aware reconciliation policy configured for a space (default RECENCY if unset).

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_reconcile_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior — that RECENCY is the effective value when no policy is configured — but leaves 'source-aware' and how a policy is resolved undefined.

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?

A single front-loaded sentence with no filler. It could have used one more short clause to explain how the space is identified, but nothing present is wasted.

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

Completeness3/5

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

Output schema exists, so return values need not be described, and all three params are optional with defaults. However, with 0% parameter coverage and a description/schema mismatch around 'space' versus run_id/user_id/agent_id, an agent cannot tell how to point the tool at a specific space.

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

Parameters2/5

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

Schema coverage is 0%, so the description must carry parameter meaning and it carries none: run_id, user_id, and agent_id are never mentioned. Worse, the description scopes the tool to a 'space' while the schema exposes no space parameter, leaving the caller to guess how the target is selected.

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?

States a specific verb ('Show') and a specific resource ('source-aware reconciliation policy configured for a space'), plus the effective default. An agent can distinguish it from set_reconcile_policy by the read framing, though the description never names that sibling explicitly.

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 when-to-use or when-not-to-use guidance, and no pointer to set_reconcile_policy for modification or to check_before_act for applying the policy. The read-only framing implies usage, but nothing is stated.

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