Skip to main content
Glama

weekly_brief

This week's official games and TCG story seeds, each marked confirmed or rumoured, with a cited official URL. Costs $0.01 USDC (x402).

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

Input Schema

NameRequiredDescriptionDefault
weekNo
franchiseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add two genuinely useful behavioural facts: the call is paid ($0.01 USDC via x402) and each returned item is tagged confirmed or rumoured with a cited URL. It does not explain how payment is settled, what happens on an unpaid call, or what the default week is when the parameter is omitted. The response is described because no output schema exists, which earns credit but leaves the payment mechanics opaque for a mutation-adjacent paid endpoint.

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?

One dense sentence with the subject front-loaded and no filler; the cost note is correctly appended as a secondary detail. Minor cost for the unexplained 'story seeds' term, which forces interpretation.

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-required-parameter tool with no annotations and no output schema, the description covers what comes back and what it costs, which is the core of the contract. It leaves notable gaps on week formatting, franchise filtering behaviour, and payment flow, which are the things an agent would most likely get wrong on a first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across both parameters, so the description must compensate and largely does not. 'This week's' hints that week is optional and defaults to the current week, but the string format (ISO week, date, label) is never stated. The franchise enum is passed over entirely, leaving the agent to guess whether 'game' scope, 'other', and the 'retail-sale'/'jellycat' values relate to the brief or silently filter it.

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 a specific resource and scope: this week's official games and TCG 'story seeds', each with a confirmed/rumoured flag and a cited official URL. That is enough for an agent to know this is a weekly editorial digest rather than raw stock data. It stops short of a 5 because 'story seeds' is unexplained jargon and it never distinguishes itself from the nearby tcg_calendar sibling.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative named. The only implied guidance comes from the 'this week's' phrasing, which suggests a current-week digest rather than a calendar lookup, but an agent has to infer that against tcg_calendar and next_drops on its own.

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