Skip to main content
Glama

The full face

meta_build
Read-onlyIdempotent

The #1 product in every category of a section put together, with the total US price. face = a full-face routine.

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.
sectionNoface (the full-face routine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description does add real behavior: the result is a per-category set of #1 products plus an aggregate US price total, which is meaningful since there is no output schema. It stops short of saying how many categories are returned or how the total is computed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the first sentence is grammatically tangled and must be re-parsed to extract the action, while the second sentence duplicates schema content rather than front-loading the key distinction from sibling tools.

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 does the minimum by naming the returned contents (top product per category plus total US price). It leaves open what a "section" can be, whether only "face" is valid, and how the aggregate is derived – gaps an agent would care about for a composite ranking tool.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, and the description's "face = a full-face routine" merely repeats the schema's own description of the section field. It adds nothing about the month parameter or about valid section values beyond the single example.

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 conveys an aggregation concept – the top product from each category of a section bundled with a total US price – but the phrasing "put together" is awkward and never states a clean verb+resource. It also fails to contrast itself with the obvious sibling best_in_category, leaving the agent to guess how the two differ.

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 when-to-use guidance, no prerequisites, and no named alternative such as best_in_category or get_ranking. The only guidance-like content is a gloss on the section value, which is usage of a parameter, not selection between tools.

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