Skip to main content
Glama

Startups Españolas press desk

Terms and prices

ver_condiciones
Read-onlyIdempotent

Returns the terms: free allowance, package prices, labelling of paid and free releases, what is not published, how the process works. Read only. Call before enviar_nota.

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

Input Schema

NameRequiredDescriptionDefault
languageNoAnswer language, default es.

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so "Read only" adds nothing beyond structured data. The genuinely additive behavioral content is the workflow precondition (call before enviar_nota) and the implied scope of the response, but side effects and whether terms can change between calls go unaddressed.

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?

Front-loaded with the verb and a compact enumeration of return contents, followed by two short directives. The "Read only" clause is redundant against the annotations and is the one sentence that does not earn its place.

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?

No output schema exists, and the description compensates by listing what the response covers, which is what an agent needs to decide whether the result answers its question. With annotations covering safety and the schema covering the single parameter, the remaining gap is minor.

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?

Only one optional parameter (language) exists at 100% schema description coverage, including an enum and the default value, so the schema fully carries parameter semantics. The description says nothing about language handling, which is acceptable but adds no value.

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?

States a specific verb (returns) and resource (the terms), then enumerates the concrete contents: free allowance, package prices, labelling of paid/free releases, unpublished items, and process mechanics. That enumeration distinguishes it from siblings like ver_medios and estado_nota, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance: "Call before enviar_nota", which tells the agent this is a prerequisite lookup. It does not state when-not to use it or name other alternatives, but for a read-only terms lookup the context is clear.

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.