Skip to main content
Glama

generate_usecase_register

Read-onlyIdempotent

Use when creating an internal AI use-case register, portfolio prioritisation view or transformation tracker. Returns value-times-feasibility priorities with governance gates and an exportable validated register.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description still adds real value by disclosing the scoring formula (value times feasibility), governance gates, and that the register is validated and exportable. It does not say how validation failures are surfaced or what happens when inputs are rejected, which matters for a tool that validates up to 10,000 records.

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, both earning their place: the first front-loads the triggering situations and the second states the returned artifact. No restatement of the tool name, no filler.

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?

An output schema exists, so return values need no prose explanation, and the description covers purpose and result adequately. The remaining gap is the dual input mode, which an agent must discover from the schema alone when deciding how to call the tool.

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 coverage is reported at 100%, so the baseline is 3. However, the schema's oneOf offers two structurally different call modes — a structured useCases array or a free-text context string — and the description never mentions this choice or when the free-text mode is appropriate, leaving the most consequential input decision undocumented.

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 names a specific deliverable — an internal AI use-case register, portfolio prioritisation view or transformation tracker — and says what the output contains (value-times-feasibility priorities with governance gates). It is clear what the tool produces, though the generating action itself is only implied by the tool name rather than stated as a verb.

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?

It opens with an explicit 'Use when' trigger naming three concrete scenarios where this is the right tool. It stops short of naming exclusions or pointing at a specific sibling (e.g. when to prefer generate_operating_model or estimate_ai_roi instead), so the routing guidance is clear but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.