Skip to main content
Glama

In-person event metadata

bpj_in_person_event_metadata
Read-onlyIdempotent

Check date order and build an in-person Event with a venue and address.

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": {
      "name": "<name>",
      "start": "<start>",
      "end": "<end>",
      "venue": "<venue>",
      "address": "<address>"
    },
    "name": "bpj_in_person_event_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
nameYes
startYes
venueYes
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds one genuinely new behavioral fact: it validates that start/end are in the correct order. It does not say what happens when validation fails (error vs. swap), nor what the build returns, which is meaningful for a constructor tool with no output schema.

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 front-loaded sentence with no filler; the validation precondition and the build action are stated up front. Its brevity is efficient, though at this length it leaves little room for the missing format and return-value detail.

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?

For a five-required-parameter constructor with no output schema and zero parameter descriptions, the definition is too thin: an agent cannot tell the expected date/address formats, what the returned Event object looks like, or how a date-order failure surfaces. Annotations cover safety but not the operational detail the schema omits.

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%; the schema supplies only titles ('Start date', 'End date', 'Name', 'Venue', 'Address') and a 240-char cap. The description names only venue and address and never specifies date format (ISO 8601 vs free text), how start/end ordering is judged, or what the name field represents — all five required parameters remain semantically thin.

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 action pair (validate date order, construct an in-person Event) on a named resource with two mandatory content elements (venue, address). The word 'in-person' implicitly separates it from the calendar-event sibling, but the description never says so outright, so differentiation rests on the reader's inference.

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: 'in-person Event' suggests this is the choice for physical venues rather than virtual/calendar events, and 'check date order' hints at a validation precondition. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. bpj_build_calendar_event).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.