Skip to main content
Glama
Sign In

The White Report

by io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewDiscussionsAdmin

Get Event Brief (Machine Format)

event_brief_get
Read-onlyIdempotent

Machine format (wr.event.v1, testnet): one sealed event brief envelope by id; version optional (default: latest version). Use event_briefs_list first if you do not have a brief 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": {
      "id": "<id>"
    },
    "name": "event_brief_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrief id, as returned by event_briefs_list.
versionNoVersion number; omit for latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Brief id."New value: +"Brief id, as returned by event_briefs_list."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description only needs to add context. It contributes the versioning default ('latest version') and the environment/format context ('wr.event.v1, testnet'), both of which are absent from the annotations. It does not describe what 'sealed' implies (signature, encryption, access 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?

Two compact sentences with the identity/format stated first and the fallback routing second; no filler. The parenthetical format string is dense but earns its place as disambiguation.

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?

With only 2 fully documented params and annotations covering safety, the core invocation needs are met. However, there is no output schema, so the description should have said more about what the 'sealed envelope' contains or whether it is encrypted/signed — that gap is the main incompleteness.

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 description coverage is 100%, and the schema already documents both id and version including 'omit for latest.' The description's version note merely restates that default rather than adding syntax or edge-case meaning, so the baseline of 3 applies.

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 (get) and resource (one sealed event brief envelope) keyed by id, plus the wire format ('wr.event.v1, testnet'). It routes the agent away from the listing sibling, though 'sealed' and 'envelope' remain unexplained domain jargon, so the exact nature of the returned object is not fully clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the precondition alternative: 'Use event_briefs_list first if you do not have a brief id,' which is a concrete when-to-use-other-tool rule. It also states the version default, but offers no guidance on when to request a specific version versus latest.

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

All The White Report 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