Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

needfix_events

Read-only

List audit events for a NeedFix entry to review its history, newest first; use it when you need past changes rather than current fields.

Instructions

List events for a NeedFix entry.

Use this for one NeedFix's audit history; use needfix_show for its current fields.

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": {
      "needfix_id": "<needfix_id>"
    },
    "name": "needfix_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return, newest first; default 100, clamped to 1-500.
needfix_idYesNeedFix id, e.g. NF-2026-01447.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / limit / description
      Added value: +"Maximum events to return, newest first; default 100, clamped to 1-500."
    • addedInput schema / properties / needfix_id / description
      Added value: +"NeedFix id, e.g. NF-2026-01447."
  2. First observedv0.1.0

TDQS

A4.2/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 the safety and scope profile is covered structurally. The description adds the useful framing that results are an audit/history view tied to a single entry, but says nothing about ordering, volume, or truncation behavior beyond what the schema already declares.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler; the primary action is front-loaded and the disambiguation follows immediately. Nothing could be removed without losing routing 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 annotations, a fully documented 2-parameter schema, and an output schema, the description covers what an agent needs to select and invoke this tool. Minor residual gap: it does not hint at result volume or pagination expectations, though the schema's limit documentation largely covers that.

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 both parameters already carry explanations including the id format and the limit default/clamping. The description adds no additional meaning about either parameter, so the baseline 3 is appropriate.

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?

Uses a specific verb ('List') plus a specific resource ('events for a NeedFix entry') and explicitly separates itself from needfix_show by contrasting audit history with current fields. An agent can identify the correct tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

States the selecting condition directly ('one NeedFix's audit history') and names the alternative that handles the competing need ('current fields' via needfix_show). This is explicit when-to-use and when-not-to-use 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