Skip to main content
Glama

Buscar Materiales en EVA

eva_buscar_materiales
Read-onlyIdempotent

Search EVA for course resources, assignments, and documents by keyword, optionally filter by course, and set maximum results.

Instructions

Busca recursos, consignas y documentos en EVA por palabra clave.

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": {
      "query": "<query>"
    },
    "name": "eva_buscar_materiales"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTérmino de búsqueda (1-100 caracteres)
limiteNoMáximo de resultados a devolver (por defecto 25)
curso_idNoID del curso (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / limite / default
      Removed value: -25
  2. Changed7 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / curso_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / curso_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / curso_id / minimum
      Added value: +1
    • addedInput schema / properties / limite
      Added value: +{
      +  "default": 25,
      +  "description": "Máximo de resultados a devolver (por defecto 25)",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "query": {
      -      "type": "string"
      -    },
      -    "resultados": {
      -      "type": "array"
      -    },
      -    "total": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "query",
      -    "resultados",
      -    "total"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the purpose statement — nothing about result ordering, whether the search spans all enrolled courses or only the one in curso_id, truncation at 'limite', or pagination. With annotations carrying the safety burden, the low score reflects the absence of any added operational detail.

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, front-loaded sentence with no filler and no repetition of schema details. It is efficient, though its brevity borders on under-specification for a tool with several siblings.

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?

Annotations cover the safety profile and the schema fully documents all parameters, and the description does enumerate the result types (recursos, consignas, documentos). Still, for a search tool among many EVA siblings, what is missing is routing guidance and any notion of result scope, which the description never addresses.

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% and all three parameters (query, limite, curso_id) are documented with types, bounds and a default, so the schema does the heavy lifting. The description only echoes the keyword aspect via 'por palabra clave' and says nothing extra about how limite or curso_id change result behavior.

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 ('Busca') with concrete resources ('recursos, consignas y documentos') and the mechanism ('por palabra clave'), so the agent understands exactly what the tool retrieves. It does not, however, distinguish itself from sibling content tools like eva_contenido_curso, eva_descargar_materiales or eva_leer_archivo, leaving overlap for the agent to resolve.

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?

'por palabra clave' implies the tool should be used when a search term is available, but nothing states when to prefer it over browsing via eva_contenido_curso or fetching a specific item with eva_descargar_materiales/eva_leer_archivo. The optional curso_id parameter hints at scoped search but no guidance is given on when to scope.

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