Skip to main content
Glama

ADS Beast

client_action_plan

Read-only

The action plan from the client's latest weekly deep-dive audit: findings labelled confirmed, inferred or hypothesis, open change proposals and open tasks.

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": {
      "client_id": "<client_id>"
    },
    "name": "client_action_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond them: results are scoped to the LATEST weekly audit rather than history, proposals and tasks are filtered to open items only, and findings carry confidence labels. It does not say what happens when no audit exists yet (empty result vs. error), which is the main unresolved behavior for a retrieve-only tool.

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 tight sentence with zero filler, front-loading the returned artifact and then enumerating its parts. The noun-phrase fragment is acceptable for a read tool. Slight cost: the confidence-label enumeration is dense but still earns its place by describing the return content.

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, the description carries the burden of describing return values, and it does reasonably well by listing the three content categories and the confidence taxonomy. It omits the empty-state behavior when no weekly audit has run, and says nothing about volume or shape of the returned plan. Adequate but not complete for a tool with a fully undocumented return payload.

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 0% for the single parameter, so the description must carry the meaning. The possessive "the client's" and the required client_id integer make the mapping obvious, but nothing is said about what happens with an invalid or unknown client_id. With only one self-evident parameter the gap is small, but it is not fully compensated.

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 resource and its provenance: the action plan from the client's latest weekly deep-dive audit, itemized into findings (confirmed/inferred/hypothesis), open change proposals and open tasks. That is far more informative than the name alone. It stops short of an explicit verb ("retrieve") and never distinguishes itself from adjacent tools such as client_goals or analytics_growth_opportunities.

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?

There is no explicit when-to-use statement, no "do not use for X", and no named alternative. Usage is only implied by the content description — an agent can infer it is the right call when it needs the current audit's action items rather than historical or goal-level data. That inference is left entirely to the reader.

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.