Skip to main content
Glama

heddle_reverify_worklist_get

Generates a worklist of items needing re-verification before claiming completion, enabling impact analysis and propagation checks.

Instructions

Render the agent worklist to recheck before claiming completion. Sibling enrichment is advisory and never gates; absence is explicit, never clean.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYes
rev_rangeNo
changed_refsNo
changed_entity_key_idsNo
depthNo
filtersNo
sort_byNo
sort_orderNo
group_byNo
limitNo
cursorNo
include_federationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes
okYes
queryYes
dataYes
warningsYes
next_actionsYes
enrichmentYes
metaYes
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. While it mentions that sibling enrichment is optional and absence is explicit, it fails to state side effects, idempotency, authentication needs, or rate limits. The cryptic second sentence adds limited value.

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 concise (two sentences) but the second sentence is cryptic and may confuse rather than clarify. It could be restructured to front-load practical usage information.

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

Completeness2/5

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

Given the tool's complexity (12 params, many siblings, output schema), the description is incomplete. It does not explain the output, how the worklist relates to other heddle tools, or how to use parameters effectively.

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

Parameters1/5

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

The input schema has 12 parameters with 0% description coverage in the schema, yet the description provides no explanation for any parameter. It does not mention 'repo', 'rev_range', or others, leaving the AI agent to guess their meaning.

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 'Render the agent worklist to recheck before claiming completion', which clearly identifies the tool's purpose: retrieving a worklist for verification. However, it does not differentiate from sibling tools like 'reverify' or others, and the term 'agent worklist' is not further clarified.

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?

The description provides no guidance on when to use this tool versus alternatives. It only states an internal behavioral property ('Sibling enrichment is advisory and never gates'), but offers no explicit when/when-not instructions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/foundryside-dev/heddle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server