Skip to main content
Glama

Ask Bestie Computers

The meta build

meta_build
Read-onlyIdempotent

The #1 product in every category of a section put together, with the total US price. pc = a full PC build, peripherals = the full desk setup.

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

Input Schema

NameRequiredDescriptionDefault
monthNoMonth as YYYY-MM. Defaults to the latest month.
sectionNopc (default) or peripherals

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuine behavior context beyond that: the result aggregates across all categories and includes a total US price. It does not describe ordering, how many items come back, or what happens when a category has no ranked product.

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?

Two sentences, no filler, with the core purpose front-loaded and the parameter glossary second. The first sentence's clause order ('in every category of a section put together') is clumsy enough to require a re-read, which is the only blemish.

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 two-optional-parameter, read-only aggregation tool with no output schema, the description covers what is produced (the top product per category plus a total US price) and the meaning of both section values. Annotations handle the safety profile, so the remaining gaps are minor edge-case behaviors rather than anything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline would be 3, but the description earns extra credit by explaining what 'pc' and 'peripherals' actually denote ('a full PC build', 'the full desk setup'), which the schema only names. The month parameter's format and default are left entirely to the schema, which documents them adequately.

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 states a specific action on a specific resource: assembling the #1 product from every category of a section along with the total US price. It also disambiguates the two section values, so an agent can distinguish it from best_in_category or list_categories. The phrasing 'in every category of a section put together' is grammatically awkward and slightly obscures that this is an aggregation tool, keeping it from a 5.

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: 'a full PC build' vs 'the full desk setup' tells the agent which section to pick for a given intent, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., best_in_category for a single category). The agent must infer that this tool is for complete build lists rather than per-category lookups.

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