Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Aniversariantes

get_birthdays
Read-onlyIdempotent

Hóspedes com aniversário durante estadias ativas ou próximas nos próximos dias.

Escopo: reports:read · Risco: read · Efeitos: Nenhum.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description specifies the scope (active or upcoming stays) and explicitly labels the risk as 'read' with 'no effects.' Since annotations already provide full safety profiles (readOnlyHint: true), the description provides helpful contextual details about the report's operation rather than hidden behavioral constraints.

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 description is highly efficient, using two sentences to cover the core functionality and the scope. The key information is front-loaded.

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?

Given that this is a specialized report tool, it is contextually complete regarding what the report returns (guests with birthdays). The description accurately captures the scope and risk profile of the function.

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 coverage is 0%. The description only mentions finding guests in 'the coming days' but does not clarify that the 'days' parameter controls the specific numeric window of those upcoming days. It fails to add meaning beyond the basic existence of the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and description are specific, clearly stating that the tool finds guests with birthdays during active or upcoming stays. This immediately defines the specific use case.

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?

While the purpose is clear, the tool does not explain when to use this report over other general guest listing or birthday-based discovery tools. It is implied that this is the correct tool for this specific scope, but no alternatives are mentioned.

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

All Arrumou Neural toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources