Skip to main content
Glama

The Marketing Vault

Plan priorities and interpret data

plan_priorities_and_data

Identifies one key priority or explains complex data in plain-English stories and recommendations. Output is saved to the Library and uses one generation. Nothing is sent or published.

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": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "plan_priorities_and_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoData for the selected template.
contextNoContext for the selected template.
detailsYesWhat the user wants, including supplied source text, goals or constraints.
audienceNoAudience for the selected template.
templateYesone-thing-prioritization: Identify the single most important priority. plain-english-data-stories: Explain data with plain-English stories and recommendations.
current_goalsNoCurrent goals for the selected template.
available_timeNoAvailable time for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.

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 this is a non-read-only, non-idempotent, non-destructive, closed-world operation, and the description adds genuinely new facts: output is persisted to the Library and consumes one generation credit. The disclosure that 'nothing is sent or published' clarifies the blast radius beyond destructiveHint=false. It stops short of saying whether repeated calls re-charge credits or how Library entries are named.

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 short sentences, capability first and side-effect/cost second, with zero filler. Every clause contributes either purpose or behavior.

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

Completeness4/5

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

For an 8-parameter generation tool with no output schema, the description covers the essentials: what it produces, where it lands, and what it costs. The remaining gap is template-dependent parameter relevance (e.g. available_time and current_goals for prioritization) and the multi-business prerequisite, which the schema mentions but the description does not reinforce.

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 100% with 8 documented parameters and an enum whose values are explained inline, so the schema already carries the semantics. The description adds nothing about how 'details', 'context', or 'data' differ, nor which parameters matter for which template. Baseline 3 is appropriate.

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 two concrete verbs (identify a priority, explain data) matched to the tool's two enum templates, so the agent knows exactly what capability is offered. It does not differentiate itself from adjacent planning or writing siblings, so an agent still has to infer why this beats 'stress_test_idea' or the 'write_*' family.

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 conditions are implied by the two named modes ('one key priority' vs 'complex data'), which is enough to trigger selection. There is no explicit when-not guidance, no named alternative, and no prerequisite (such as needing a business profile when multiple Businesses exist) surfaced in the description.

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