Skip to main content
Glama

Ver servicios

get_services
Read-onlyIdempotent

Lista los seis servicios de Kroel Graphics (identidad de marca, arte para música, publicidad, fotografía, edición de video, imprenta y código). Úsala cuando alguien pregunte qué hace el estudio o si atiende cierto tipo de proyecto. Devuelve el resumen del estudio, cada servicio con id, nombre y detalle, los precios de arranque en pesos mexicanos, cómo se cotiza y los límites (por ejemplo, Estados Unidos solo en línea).

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_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
estudioYesResumen del estudio.
limitesYesLo que el estudio no hace.
preciosYesPrecios de arranque y cómo se cotiza.
serviciosYesServicios disponibles.
precios_desdeNoPrecio de arranque por servicio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / precios / description
      Previous value: -"Cómo se cotiza."New value: +"Precios de arranque y cómo se cotiza."
    • addedOutput schema / properties / precios_desde
      Added value: +{
      +  "description": "Precio de arranque por servicio.",
      +  "items": {
      +    "properties": {
      +      "concepto": {
      +        "type": "string"
      +      },
      +      "desde": {
      +        "type": "number"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "incluye": {
      +        "type": "string"
      +      },
      +      "moneda": {
      +        "type": "string"
      +      },
      +      "servicio": {
      +        "type": "string"
      +      },
      +      "unidad": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "concepto",
      +      "desde",
      +      "moneda"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: it says the response includes the studio summary, service ids/names/details, starting prices in MXN, quoting method, and limitations such as US online-only service. The only blemish is the "seis" versus seven listed services inconsistency.

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 definition is front-loaded with purpose, then usage, then return details, and has little wasted wording. The long parenthetical service list is informative but contributes to the "seis" versus seven-items inconsistency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 tool with an output schema and safety annotations, the description covers what it does, when to use it, what it returns, and business limits. Nothing essential is missing for an agent to select and 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?

There are zero parameters and the input schema is empty, so parameter semantics are largely irrelevant. The description correctly avoids inventing parameter guidance, matching the baseline for a no-parameter tool.

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 uses a specific verb and resource: it lists Kroel Graphics services and names the topics covered. It also clarifies the scenario versus quote/contact siblings, though it does not explicitly name those alternatives. Minor count inconsistency: it says "seis servicios" but enumerates seven items.

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?

It gives clear usage conditions: when someone asks what the studio does or whether it handles a certain type of project. It does not state when not to use it or explicitly route to prepare_quote/get_contact alternatives, so guidance is clear but not exhaustive.

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.