Skip to main content
Glama

AI Opportunity Assessment

AOA AI Opportunity Assessment

aoa_ai_opportunity_assessment
Read-only

Start an AI Opportunity Assessment: a mini assessment, a discovery-call guide, or a full assessment from interview notes. Routes each request to the matching AOA tool.

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": {
      "input": "<input>"
    },
    "name": "aoa_ai_opportunity_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesAssessment request with selected route, current source evidence and conversation context when available.

Output Schema

NameRequiredDescriptionDefault
routeYes
actionYesout_of_scope for external actions or fabrication requests. prepare_report hands the request to next_tool in the same turn (the mini tool runs its own interview). ask_question for the welcome menu or one missing item.
choicesYesOptions for this question, in order; [] when the question is free text or no question is asked. Host: show them as selectable cards or buttons when the app supports choice UI, otherwise as a numbered list under message. Always keep the last option, other. When the user picks other or types instead, call this tool again with their own words.
messageYes
next_toolYesmini_report -> run_aoa_mini_assessment; discovery_guide -> create_aoa_discovery_guide; full_report -> run_aoa_full_assessment; knowledge_base -> run_aoa_knowledge_base_assessment; none for ask_question and out_of_scope.
contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context that it dispatches rather than performing the assessment, but it is ambiguous about whether a call merely returns a routing decision or actually executes the downstream assessment, and idempotentHint=false goes unexplained.

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 tight sentences with the operation and the enumeration front-loaded, and no filler. Every clause carries information an agent needs to select the tool.

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 values need not be explained, and the annotation set covers safety. However, for a router whose entire job is selection, the description leaves unclear what distinguishes the three routes or what the caller must supply to make routing succeed, which is a meaningful gap for this complexity level.

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?

With a single required parameter at 100% schema description coverage, the schema already explains that input carries a selected route, source evidence and conversation context. The description restates the route types but adds no input formatting or example beyond the schema, so baseline 3 applies.

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 a specific verb and resource ("Start an AI Opportunity Assessment") and enumerates the three route types it handles, which lets an agent tell this dispatcher apart from the concrete sibling tools (run_aoa_* / create_aoa_discovery_guide). It stops short of describing what the assessment itself produces, so the purpose is clear but not fully specified.

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?

"Routes each request to the matching AOA tool" implies this is the entry-point dispatcher, but the description never states when an agent should choose this over calling run_aoa_full_assessment or run_aoa_mini_assessment directly. Usage is inferable from the routing sentence rather than explicitly prescribed, and there are no exclusions.

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.

Resources