Skip to main content
Glama

obit_proposals

Read-only

Lists file-expiry proposals in ascending ID order with pagination and change detection; approval or rejection stays with the user.

Instructions

Lists proposals in ascending ID order; pass nextAfter as after and version to continue. changed warns when the full set changes; restart for a complete view. total counts this read. Approval and rejection belong to the user, who executes obit approve or obit reject; this server cannot decide them.

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

Input Schema

NameRequiredDescriptionDefault
afterNoPrevious nextAfter (decimal ID string); omitted starts at the beginning
limitNoResults per page; 0 uses 200; maximum 200
versionNoPrevious page version; a different current set returns changed and a warning to restart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and non-idempotent, and the description adds meaningful behavior on top: the pagination continuation protocol, the semantics of the changed warning, and the important clarification that total counts only this read rather than the full set. It still says nothing about the shape of a proposal record, but the behavioral gaps that matter for correct invocation are covered.

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?

Front-loads the core verb and resource, then layers paging, staleness, counting, and the permission boundary with no filler. The middle-sentence semicolon packing is dense but each clause carries distinct 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 no output schema, the description covers the paging loop, the changed/restart recovery path, and what total means, which is what an agent needs to drive this tool. The main residual gap is the content of a proposal record, which the agent must discover from the response.

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%, so all three parameters are already documented, and the description largely restates them ('pass nextAfter as after and version to continue'). It does add the linkage that after and version are used together for continuation, but that is a small increment over the schema.

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 and resource ('Lists proposals') plus the ordering guarantee ('ascending ID order'), so an agent knows exactly what the call returns. It does not explicitly contrast itself with the sibling obit_list, leaving a small ambiguity about which listing tool to pick.

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?

Gives clear operational context: pass nextAfter as after plus version to page through, and restart when changed is flagged. It also sets a scope boundary by stating that approval/rejection is not this server's job, though it never names an alternative listing tool or an explicit when-not-to-call condition.

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