Skip to main content
Glama
forbiz-mcp

forbiz-mcp

Queue of pending items

forbiz_prompts
Read-only

List waiting items grouped by decision, feedback, waiting, or review date, showing timing and available commands to act now.

Instructions

Everything waiting, grouped (needs_decision, needs_feedback, waiting, needs_review_date), each with timing.available_commands: what you may do right now (GET /prompts).

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

Input Schema

NameRequiredDescriptionDefault
groupNoOnly one group, e.g. needs_feedback

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the grouping taxonomy (needs_decision, needs_feedback, waiting, needs_review_date) and the timing.available_commands semantics, which tell the agent the response shape beyond what annotations convey.

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 compact sentence front-loads the resource and its grouping, with the endpoint appended. The dotted 'timing.available_commands' notation is slightly cryptic, but nothing is wasted.

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?

There is no output schema, so the description must carry the return-shape burden, and it does so by naming the groups and the timing/available_commands fields. It omits ordering or pagination behavior, but for a read-only queue view with full annotation coverage it is largely complete.

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

Parameters4/5

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

Schema coverage is 100% for the single optional 'group' parameter, so baseline is 3. The description goes further by enumerating the concrete group values that the filter accepts, adding meaning beyond the schema's terse 'Only one group, e.g. needs_feedback'.

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 clearly conveys that this returns the full queue of pending items grouped by category, effectively a list/get of waiting work. The verb is implicit ("Everything waiting") rather than a crisp action word, and it does not explicitly contrast itself with siblings like forbiz_next, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer that this is the tool to call for a complete view of the pending queue, versus forbiz_next for the next single item. There is no explicit when-to-use/when-not statement and no named alternatives, so it stays at the minimum-viable level.

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