Skip to main content
Glama

What is for sale

get_offers
Read-onlyIdempotent

Premium is the only paid offer: 49 USD per month, every published analysis while the subscription is active. Review and rights limits remain; there is no agent 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": "get_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the offer is recurring while the subscription is active, review and rights limits still apply, and no payment path exists for an agent. It does not state the shape of the response, which is a minor gap with no output schema.

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?

Key facts are front-loaded: the offer name, the price, and what the subscription buys. The phrase 'Review and rights limits remain' is compressed to the point of being vague and consumes space without telling the agent what those limits are.

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 a zero-parameter, read-only pricing lookup with no output schema, the description covers what is on offer, its cost, its duration and its constraints. What is missing is only the concrete return shape and the meaning of the unexplained rights limits.

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 the schema carries nothing an agent must interpret and the baseline applies. The description correctly introduces no parameter discussion, avoiding noise.

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 identifies the resource precisely: the single paid offer (Premium, 49 USD/month) and what it includes. There is no explicit verb such as 'list' or 'return', but with a one-item catalog and a sibling set containing no other pricing tool, the purpose is unambiguous.

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 implied rather than stated: an agent would call this to learn pricing or to answer 'what is for sale'. The line 'there is no agent payment' usefully signals that no transaction can follow, but no alternative tool is named and no explicit when-to-use trigger is given.

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.