Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ofertas del aula

list_offers
Read-only

Retrieve classroom offers by ID, including type, discount, validity, available spots, and status, to review current promotions without making changes.

Instructions

[Administrador del aula · solo lectura] Lista las ofertas del aula con su tipo, descuento, vigencia, cupos y estado.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "classroom_id": "<classroom_id>"
    },
    "name": "list_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context by listing the returned offer attributes and the administrator scope, but does not disclose ordering, pagination, empty-result behavior, or any permission constraints beyond 'Administrador del aula'.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted wording. The bracketed context tag and the list of returned fields are both informative and compact.

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 simple one-parameter read-only list tool, the definition gives enough to call it correctly: the classroom scope, read-only nature, and fields returned. Annotations cover safety and the schema fully documents the parameter. Minor gaps around ordering, pagination, and explicit alternative routing keep it from being fully complete.

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?

The schema fully documents the single classroom_id parameter, including its UUID format and the label 'Aula'. The description's phrase 'del aula' reinforces meaning but does not add syntax or scoping details beyond what the schema already provides. Baseline 3 is appropriate when schema description coverage is 100%.

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 states a specific verb and resource: list classroom offers, scoped to a classroom and marked read-only. It also names the offer fields returned (type, discount, validity, slots, status). It is clear, though it does not explicitly distinguish itself from offer-mutating siblings such as create_offer or update_offer beyond the word 'Lista'.

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?

Usage is implied by '[Administrador del aula · solo lectura]' and 'Lista', which suggests an admin inspecting offers in a classroom. However, it provides no explicit when-to-use guidance, no exclusions, and no named alternative such as list_sales or get_course.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools