Skip to main content
Glama

Phoenix about

phoenix_about
Read-onlyIdempotent

Public offers in plain language, with request links. Read only. Does not take an order or a payment.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so 'Read only' merely restates structured data. The added clause 'does not take an order or a payment' is genuinely beyond the annotations because it rules out domain-level side effects, and 'with request links' hints at the response contents, but nothing is said about permissions, freshness, or result shape.

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?

Three short, front-loaded sentences with no filler; the read-only assurance follows the content statement in a sensible order. A small amount of space is spent restating the read-only annotation.

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?

For a zero-parameter, non-destructive tool this is close to adequate, and no output schema exists so return values need not be detailed. Still, with no output schema the description could say what an 'offer' entry and a 'request link' look like, and the mismatch with the 'about' name leaves identity uncertainty.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline applies. No parameter text is needed or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a resource ('public offers in plain language, with request links') but never connects it to the tool's name/title 'Phoenix about', so an agent cannot tell whether this is an informational overview, a catalog, or something else. The resource is named but the operation and scope stay vague relative to siblings like content_offers or local_offer.

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?

'Does not take an order or a payment' implies when NOT to use it (ordering/payment flows), which is useful negative guidance. However, it names no alternative among the many offer-related siblings and gives no positive trigger such as 'use this to get an overview before picking a specific offer'.

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