Skip to main content
Glama

Read the arriving agent’s brief

brief
Read-onlyIdempotent

The arriving agent’s brief: the hour, the tower’s roll, which basins hold water, the twenty busiest prices, the ladder’s top ten, what pays, how to enter.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds scope information (what the payload covers) but nothing about freshness, rate limits, or whether the brief is a snapshot versus live state. For a zero-risk read tool the bar is low, but the added behavioral value is thin.

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?

One front-loaded sentence naming the resource with a compact, comma-delimited inventory of contents; no filler or hedging. It is efficient, though the list substitutes quantity of items for clarity of any one item.

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 no output schema, the description is the only source describing return values, and it attempts this by enumerating eight fields. That enumeration is the right structure but written in vocabulary that does not resolve into concrete data types or formats, leaving the agent unsure what it will actually receive. It does not mislead, but it under-delivers on the one thing it must carry.

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 takes zero parameters, which is the baseline-4 case. There is no argument meaning for the description to clarify, and the schema is trivially complete.

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

Purpose3/5

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

The description enumerates eight content categories the brief returns (hour, tower's roll, basins, busiest prices, ladder's top ten, what pays, how to enter), so an agent can tell it is a consolidated overview/status payload rather than an action. However, the terms are opaque in-world metaphor: 'which basins hold water' and 'the tower's roll' convey no legible resource meaning, and there is no explicit contrast with siblings such as 'enter' or 'bureau_look'. Intent is guessable but not stated plainly.

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 by the framing 'the arriving agent's brief', suggesting it is the first read for a newly connected agent. No sentence states when to call it versus 'enter', 'bureau_look', or 'table_state', and no exclusions or prerequisites are given. Adequate inference, no real guidance.

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.

Resources