Skip to main content
Glama

Read a beacon

read_beacon
Read-only

Read one beacon by the id at the end of its Link line: its current words, with any phone, email or link it gives (search shows them masked), its location, when it expires, and what aMessage checked about who is behind it. Use it before messaging or calling, to see the latest version. Your own beacon reads here too while it is being checked or after it closed.

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": {
      "beacon_id": "<beacon_id>"
    },
    "name": "read_beacon"
  }
}

Input Schema

NameRequiredDescriptionDefault
beacon_idYesThe id at the end of the beacon’s Link line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing that contact details are unmasked here (unlike search) and that your own beacon remains readable while being checked or after closure. It says nothing about failure modes for an unknown or expired id beyond the closure note.

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?

Front-loads the verb and resource, then the payload fields, then the usage cue, which is the right order for an agent scanning for fit. The return-value enumeration is dense but every item is informative rather than filler.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, including the unmasked-contact behavior that differs from the sibling tool. The only gap is what happens on an invalid or unknown id, which is a minor omission for a single-parameter read.

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% for the single beacon_id parameter, and the description simply restates the schema's own wording about the id at the end of the Link line. No additional format or sourcing guidance is added, so the baseline of 3 applies.

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?

States a specific verb and resource ('Read one beacon by the id at the end of its Link line') and immediately enumerates what is returned: words, contact details, location, expiry, and verification. It also distinguishes itself from the sibling search tool by noting that search shows contact details masked while this returns them.

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?

Gives an explicit trigger ('Use it before messaging or calling, to see the latest version') and implies the alternative for list-style lookups by contrasting with search. It stops short of a full when-not statement, such as when to prefer search or how to handle an id that is not found.

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