Skip to main content
Glama

Get AI conditions

get_ai_conditions
Read-only

Read what Ankra's AI keeps seeing and how it acts on it. report picks it: conditions (each recurring problem on a subject: occurrences, tickets filed, whether it is chronic; the twin of ankra ai conditions list), condition (one condition's timeline of tickets, probes and playbook runs; needs condition_id; the twin of ankra ai conditions get), playbooks (the steps the AI runs for a kind of condition, adopted or offered as Ankra's templates) or handoffs (platform alerts passed to engineering, with status open, filed or resolved). Needs the organisation's AI experience. A caller confined to one project reads only its conditions and is refused the other three reports. Read-only: adopting or retiring a playbook and acknowledging a handoff are an administrator's acts, not offered here.

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": {
      "report": "<report>"
    },
    "name": "get_ai_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoconditions: rows to return, 1 to 500 (default 100).
reportYesWhich listing to read.
statusNohandoffs: a comma-separated list of open, filed and resolved (default all).
chronicNoconditions: only the chronic ones.
condition_idNocondition: the condition (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

The readOnlyHint annotation already declares the safety profile, and the description reinforces it by naming the write operations it deliberately omits and the authorization requirement ('needs the organisation's AI experience'). The most valuable addition is the scoping behaviour — a project-confined caller reads only conditions and is refused the other three — which is not derivable from annotations. It stops short of describing volume, pagination or result sizing, so against an already-covered safety profile it is solid but not exhaustive.

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?

The content is front-loaded, with the core purpose in the first sentence and the report taxonomy immediately after, and no sentence is filler. The long parenthetical, semicolon-chained enumeration of report modes is dense and takes effort to parse, which costs it the top mark.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing what comes back, and it does so for each mode — occurrences and ticket counts for conditions, a timeline of tickets, probes and playbook runs for a condition, statuses for handoffs. Combined with the stated preconditions and read-only boundary, an agent has everything needed to invoke it correctly.

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%, so the baseline is 3, but the description genuinely adds meaning beyond the schema's bare 'Which listing to read' by explaining what each report value actually contains. It also surfaces the conditional dependency on condition_id for the 'condition' report, which the schema only implies through its per-parameter note.

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?

The description opens with a specific verb and resource ('Read what Ankra's AI keeps seeing and how it acts on it') and then enumerates the four concrete report modes, each with its own subject matter. An agent can tell immediately that this is a read tool for AI conditions, playbooks and handoffs rather than settings, spend caps or endpoints as the sibling names suggest.

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?

It states the selection rule for each report value ('conditions' = recurring problems per subject, 'condition' = one condition's timeline and needs condition_id, 'playbooks' = steps the AI runs, 'handoffs' = alerts passed to engineering), so the agent knows which enum value matches its need. It also gives an explicit when-not: adopting or retiring a playbook and acknowledging a handoff are administrator acts 'not offered here', and it discloses the project-confinement rule that refuses three of the four reports.

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.