Skip to main content
Glama
Sign In
Brivo Velocity

Brivo Velocity

by ThatGuyinIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Holidays: Get_holiday

Read-only

Retrieve a single holiday by its Brivo holiday ID to view holiday details.

Instructions

Retrieve a single holiday by id.

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": {
      "holidayId": "<holidayId>"
    },
    "name": "Holidays: Get_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
holidayIdYesThe Brivo holiday id, e.g. from Holidays: List_holidays.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on not-found behavior, error handling, or whether the holiday is returned in full or summarized.

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?

One front-loaded sentence with zero filler or redundancy. Every word earns its place for a single-parameter lookup tool.

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?

For a trivial read-only lookup with one fully documented parameter and no output schema, the definition covers the essentials. The only missing context is error/not-found behavior, which is minor at this complexity level.

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 coverage is 100% and the single holidayId parameter is fully documented in the schema, including its origin (from Holidays: List_holidays). The description's 'by id' adds no syntax, format, or accepted-type detail beyond what the schema already states.

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 (retrieve) and resource (a single holiday) plus the lookup key (by id), which implicitly separates it from the sibling List_holidays. It is clear but does not explicitly name or contrast with that sibling.

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?

Usage is only implied: 'single holiday by id' signals a point lookup versus the bulk List_holidays, and the schema description hints the id comes from List_holidays. There is no explicit when-to-use, when-not-to-use, or named alternative in the description itself.

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