Skip to main content
Glama

Ask Bestie Cars

No car bundle

meta_build
Read-onlyIdempotent

Unavailable: cars are alternatives, not a collection to buy together.

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.
sectionNoNone; cars are alternatives, not a bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that the tool is a no-op refusal, which is consistent with the read-only annotations, but it does not say what a call actually returns or whether it errors.

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?

A single short sentence with the unavailability stated up front and the rationale immediately after. Nothing is padded, though the sentence is so terse that it omits any actionable redirect.

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 two-parameter, no-output-schema stub, the definition covers the essential fact (it is unavailable and why) and is consistent with its annotations. It is still incomplete in that an agent gets no guidance on what to call instead or what a call to this tool actually does at runtime.

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 description coverage is 100%, so both parameters (month, section) are already documented in the schema, including the YYYY-MM pattern and the default. The description adds no additional meaning about how month or section affect behavior, so the baseline of 3 applies.

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 states the tool is unavailable and gives a reason (cars are alternatives, not a bundle), which tells an agent this is a refusal/stub rather than a functional build tool. However, it never states what the tool would do or what resource it operates on, so the purpose is only inferable from the name meta_build and the title.

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?

It implies the correct behavior is to treat cars as alternatives rather than a collection, which nudges an agent away from bundling, but it never names a concrete alternative sibling (e.g. compare_products or get_product) or states the condition under which another tool should be called. Usage is implied rather than directed.

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