Skip to main content
Glama
Sign In
WaveMind Preset MCP

WaveMind Preset MCP

by Hemir95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Categorias Biblioteca

categorias_biblioteca

Inventory NAM categories and IR collections with counts to inspect the organized capture library.

Instructions

Inventory the organized library: NAM categories and IR collections with counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Inventory" implies a read-only enumeration and the phrase "with counts" hints at aggregate return content, but nothing states whether the result is exhaustive, paginated, permission-scoped, or cached. It adds modest behavioral signal but leaves the important traits unstated.

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 short sentence with the core action front-loaded and no filler. It is efficient, though the unexplained acronyms cost a little clarity per word spent.

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?

An output schema exists, so return values need not be re-explained, and the input is empty. The remaining gap is conceptual: an agent cannot map "NAM categories" or "IR collections" to the domain without external knowledge, so the definition is not self-sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description does not need to explain syntax or formats because no input exists.

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?

"Inventory the organized library" gives a specific verb+resource, and it enumerates the contents (categories and collections with counts), which separates it from search-style siblings like buscar_biblioteca. The cryptic acronyms "NAM" and "IR" are never expanded, so part of the resource is opaque to an agent that lacks domain context.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of how this differs from buscar_biblioteca or list_param_ids. An agent must infer from the name alone that this is a browse-and-count tool rather than a search tool.

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