Skip to main content
Glama

Amplify status

amplify_status
Read-only

Connected channels, languages, mode, guardrails, post counts and what has performed best for this customer. Needs the customer's Growth Employee key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the call is scoped per customer and requires a Growth Employee key, an authentication prerequisite an agent would otherwise have to discover by failing. It does not mention rate limits or freshness of the returned data.

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 sentences, no filler: one enumerates the returned fields and one states the prerequisite. It is front-loaded with the substantive content rather than preamble.

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?

There is no output schema, so the description carries the burden of describing return values, and it does by listing the fields returned. Combined with the auth prerequisite and the per-customer scope, an agent has enough to call it correctly; only data freshness and response shape remain unspecified.

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?

The tool takes no input parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The only 'input-like' detail it adds, the required Growth Employee key, is auth context rather than a schema parameter.

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 enumerates exactly what the tool surfaces for a customer: connected channels, languages, mode, guardrails, post counts and top performers. That is a concrete resource scope an agent can distinguish from siblings like amplify_list_posts or amplify_create_campaign. It stops short of a leading verb (e.g. 'Returns a status summary'), so it is clear but slightly indirect.

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: a 'status' tool is evidently for getting an overview before acting, and the prerequisite 'Needs the customer's Growth Employee key' is stated. There is no explicit when-to-use framing, no exclusions, and no named alternative for post-level or campaign-level detail.

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