Skip to main content
Glama

generate_operating_model

Read-onlyIdempotent

Use when building an internal product operating model with OKRs, roadmaps and team topology. Returns a validated model, ownership checks and team interactions for portfolio and delivery tools.

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": {
      "teams": "<teams>"
    },
    "name": "generate_operating_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
okrsNo
teamsYes
roadmapNo
productsNo
interactionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 the safety profile is covered. The description adds real context beyond that: the tool returns a 'validated model' plus 'ownership checks', implying it performs consistency validation rather than just echoing input, and it hints at downstream consumption by portfolio and delivery tools. It does not say what happens when validation fails or how problems are surfaced, which keeps it below 5.

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?

Two sentences, front-loaded with the 'Use when' trigger and followed by a return-value sentence. No filler or restatement of the name. The second sentence is slightly compressed ('for portfolio and delivery tools'), but nothing is wasteful.

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

Completeness3/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-value detail is correctly omitted, and the safety profile comes from annotations. What is missing is invocation-critical context for a deeply nested five-parameter schema: whether ids must cross-reference across okrs/teams/roadmap, whether products and interactions are optional, and what validation failures look like. Adequate, but not complete for a tool of this structural complexity.

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 0%, so the description must carry the semantic load for five parameters. It names three of the five concept areas (okrs, roadmap, teams) and gestures at interactions via 'team interactions', but never mentions 'products' and never explains the cross-reference constraints such as okr.teamId or roadmap.okrId pointing at valid team/OKR ids. The nested enums (team type, cognitiveLoad, horizon, interaction mode) are self-explanatory from the schema, so a 3 is fair rather than a 2.

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 verb-and-resource pair ('building an internal product operating model') and enumerates the constituent artifacts: OKRs, roadmaps and team topology. That domain is clearly distinct from the sibling tools (AI readiness, cost, ROI, delivery health), so an agent can route correctly without opening the schema. It stops short of an explicit contrast with any sibling, which keeps it at 4.

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?

'Use when building an internal product operating model with OKRs, roadmaps and team topology' gives a concrete triggering condition rather than a vague category. There is no when-not guidance and no named alternative for adjacent tasks such as scoring delivery health, but the stated context is specific enough to select on.

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.