Skip to main content
Glama

What has worked

get_performance_digest
Read-onlyIdempotent

Measured post performance with sample sizes: findings, top posts, plan deltas and the prompt block content generation uses. Read this before proposing new content so the advice is grounded in this workspace's numbers.

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_performance_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
plan_idNoRestrict to one plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds useful non-obvious context that returned data includes sample sizes and the internal prompt block used for generation, but says nothing about cost, latency, or how expensive a 365-day range might be.

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?

Two sentences, front-loaded with the resource and payoff, no filler. The middle clause is a dense list, but every item names real returned content rather than padding.

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 must carry the return contract, and it does name the four main payload sections. It does not say how the data is shaped or sized, or how plan deltas relate to the plan_id parameter, which leaves an agent guessing at structure.

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?

Only two parameters and the schema already documents plan_id ('Restrict to one plan') while days carries a default of 30 plus min/max bounds. The description adds no parameter detail, but at this parameter count and 50% coverage the names and bounds carry the meaning adequately, so the gap is minor.

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+resource: measured post performance returned as findings, top posts, plan deltas and the generation prompt block. That is concrete enough to know what comes back, but it never distinguishes itself from overlapping siblings like get_post_performance or get_top_posts, which an agent will see in the same catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage condition: 'Read this before proposing new content so the advice is grounded in this workspace's numbers.' That is a genuine when-to-use rule. It stops short of exclusions (e.g. when to prefer get_top_posts or get_post_performance instead), so it is clear context without alternatives.

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