Skip to main content
Glama
andrsnrua
by andrsnrua

blackboard_search_multi_course_announcements

Read-onlyIdempotent

Search keywords in Blackboard announcements across up to 10 courses. Returns matching announcements and flags any courses not searched or restricted.

Instructions

Busca términos en anuncios de 1 a 10 secciones, conserva courseId y señala cursos no consultados o restringidos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
courseIdsYes
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds that results flag unqueried or restricted courses, which is useful behavioral context. However, it does not explain what 'restricted' means, whether partial results are returned, or the format of the courseId preservation.

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 well-packed sentence with no filler. It front-loads the action and scope, though it could be clearer about the output contract.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotation coverage beyond safety hints, and 0% parameter description coverage. The description is too thin to fully explain a multi-course search tool's behavior, parameter constraints, and result handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions '1 a 10 secciones' (mapping to courseIds maxItems=10) and implies a search term (query), but leaves maxResults entirely undocumented and does not clarify the required format of courseIds.

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 states a verb ("Busca") and a resource ("anuncios"), and adds a scope hint ("de 1 a 10 secciones"). However, it does not state what it returns beyond preserving courseId, and the phrase "señala cursos no consultados o restringidos" is vague. It is distinguishable from sibling blackboard_search_announcements only by the implicit multi-course scope.

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?

No when-to-use guidance is provided. It does not say when to prefer this over blackboard_search_announcements or blackboard_list_announcements, nor does it describe prerequisites such as needing prior course IDs or authentication.

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