Skip to main content
Glama

Get Agent Office Plan

get_agent_office_plan
Read-onlyIdempotent

[read] One custom AI Office scenario (by agent_office_plan_id or agent_office_plan_uuid) with its steps (a plan graph also its nodes and edges), dependencies, step keywords, targets, AI accounts, step agents (empty = random of the role) and step settings.

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

Input Schema

NameRequiredDescriptionDefault
agent_office_plan_idNo
agent_office_plan_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral value by disclosing the expanded relations and the semantic quirk 'step agents (empty = random of the role)', which an agent could not infer from structured fields.

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 dense sentence, front-loaded with the [read] marker and the resource, then the payload contents. The nested parentheticals are slightly cluttered but every clause conveys a returned field.

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?

With no output schema and 0% parameter coverage, the description does a reasonable job enumerating returned fields, but leaves a critical ambiguity: both identifier parameters are optional in the schema, and the description never explains what happens if neither or both are supplied.

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 compensate. It tells the agent the plan can be addressed by `agent_office_plan_id` or `agent_office_plan_uuid`, which is useful, but it does not say whether both are optional, whether at least one is required, or how conflicts between the two are resolved.

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?

States a specific verb ('get') and resource ('One custom AI Office scenario') and enumerates what the payload includes (steps, nodes/edges, dependencies, targets, AI accounts, step agents, settings). 'One' implicitly contrasts with the sibling list_agent_office_plans and get_agent_office_film, though no sibling is named explicitly.

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: fetch a single plan by id or uuid. There is no explicit guidance on when to prefer this over list_agent_office_plans or validate_agent_office_plan_graph, and no prerequisites or failure conditions are stated.

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.