Skip to main content
Glama

Get the decision brief for a category

get_brief_summary
Read-onlyIdempotent

The pick, picks by need, the criteria that matter and the brands that count for one product category, with provenance (model, generation, knowledge cutoff) and the source URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "get_brief_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine context by naming provenance fields (model, generation, knowledge cutoff) and the source URL, which tells the agent the brief is versioned evidence rather than a live query. It says nothing about behavior for unknown/ambiguous categories or how stale a cached brief may 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?

One dense sentence with no filler, front-loaded on what the caller receives. The comma-separated clause chain is slightly hard to parse but nothing is superfluous.

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 characterize the return value — it does so at a high level but not structurally (field names, shape, whether provenance is per-pick or per-brief). For a one-parameter read tool this is workable but leaves the caller guessing about both input format and response shape.

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% for the single required parameter, so the description carries the full burden — yet 'one product category' does not clarify whether `category` is a display name, slug, or ID, or how to resolve it (presumably via search_categories). This is the definition's weakest link.

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 (a decision brief) and enumerates its contents: the pick, picks by need, criteria, brands, provenance and source URL, scoped to one product category. That is concrete enough to distinguish it from a single-pick call, though it never explicitly contrasts with get_pick or search_categories.

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 statement of when to call this versus get_pick (single pick) or search_categories (discovery), both of which are obvious alternatives. Usage must be inferred from the word 'brief' and the enumerated return contents.

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