Skip to main content
Glama
Sign In
MCP Advbox Server

MCP Advbox Server

by JonasSousaAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

advbox_get_birthdays

Identify customers with birthdays in the current month to enable timely engagement and personalized outreach.

Instructions

Get customers with birthdays in the current month

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'gets' customers, implying a read operation, but does not disclose return format, pagination, sorting, timezone handling, or any side effects. For a simple read, this is minimal but lacks important behavioral context.

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, clear sentence with no filler. Every word contributes to the purpose, and it is front-loaded with the action and resource.

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?

The tool is simple with no parameters and no output schema, but the description could provide more context, such as what customer fields are returned, whether 'current month' follows a specific timezone, or whether results are ordered. These gaps make it adequate but not complete.

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 has zero parameters, and schema coverage is 100%, so the description is not required to explain parameters. The baseline for 0 parameters is 4, and the description does not need to compensate anything here.

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 description 'Get customers with birthdays in the current month' uses a specific verb ('Get'), identifies the resource ('customers'), and adds a distinct qualifier ('birthdays in the current month') that clearly differentiates it from sibling tools like list_customers and get_customer.

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?

The purpose implies usage (when you need customers with birthdays this month), but there is no explicit guidance on when to use it versus alternatives like list_customers. No when-not or alternative tool is mentioned, so it relies on the agent to infer utility.

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