Skip to main content
Glama

Gilroy Motor — electric motorcycles (Chile)

Condiciones de compra

get_terms
Read-onlyIdempotent

Envío por zona en Chile, formas de pago, garantía, devoluciones, licencia requerida, qué incluye el precio, contacto y canales oficiales.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-open-world operation, so the description does not need to repeat that safety profile. It usefully adds content scope by listing the policy areas the response covers, including jurisdiction-specific shipping details for Chile and official contact channels. However, it says nothing about output format, freshness, or whether the terms are static, leaving some behavioral context unstated.

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?

The description is a single compact sentence that front-loads a dense list of policy topics with no filler or redundant wording. Each listed item corresponds to a plausible section of the terms, so the content earns its space. The fragment style lacks a lead-in verb, but overall it is efficient and easy to scan.

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 zero-parameter, read-only informational tool with no output schema, the description gives an adequate inventory of what the response will cover. Annotations handle the safety and openness profile, and the topic list handles content scope. The main remaining gap is that it does not explicitly say the tool returns terms text rather than performing an action, but the context makes that reasonably clear.

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?

The tool takes zero parameters and the description correctly does not invent any. With no input schema fields to clarify, there is no parameter semantics gap to compensate for, so this dimension has a solid baseline. The description could have said that no arguments are needed, but the empty schema already makes that clear.

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 enumerates the policy topics covered (shipping by zone in Chile, payment methods, warranty, returns, license, price inclusions, contact channels) but never states what the tool does with a verb or resource phrase. Combined with the name get_terms and the title 'Condiciones de compra', an agent can infer it returns store terms, yet the description alone leaves the action implicit. It is not mistaken for the model-related siblings, but the purpose is only moderately clear.

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 guidance on when to call this tool, when not to call it, or which sibling to use instead. The topic list implies it is a policy lookup, but the agent must infer that from context rather than from stated usage conditions. No alternatives or exclusions are named.

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