Skip to main content
Glama

signal-bureau

by io.github.evolutionlabs-dev
OverviewDiscussionsAdmin

ask

Ask what the tracked record shows about a named entity or unfolding event: what changed, what the record holds now, and which sources corroborate it. Not general knowledge or history — grounding is live tracked coverage. 25 questions a day per network address need no key; then each costs one Read on a free key (POST /api/keys). Async — a ticket in ~1s, collected with get_answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freshNoForce a new synthesis instead of the maintained record's recent answer to the same question (default false — shared state is the default)
watchNoOptional. The Watch this question is asked under. Recorded as declared on the answer's `replay` block. A malformed value is named in `replay.declared.rejected`, never applied. Same field as POST /api/ask.
observerNoOptional. The observer this question is asked as (e.g. an observer list_standard_watches names). Recorded as declared on the answer's `replay` block; default "public". A malformed value is named in `replay.declared.rejected`, never applied. Same field as POST /api/ask.
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / observer
      Added value: +{
+  "description": "Optional. The observer this question is asked as (e.g. an observer list_standard_watches names). Recorded as declared on the answer's `replay` block; default \"public\". A malformed value is named in `replay.declared.rejected`, never applied. Same field as POST /api/ask.",
+  "type": "string"
+}
    • addedInput schema / properties / watch
      Added value: +{
+  "description": "Optional. The Watch this question is asked under. Recorded as declared on the answer's `replay` block. A malformed value is named in `replay.declared.rejected`, never applied. Same field as POST /api/ask.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations present, the description still adds substantial behavior the annotations do not carry: asynchronous execution (a ticket in ~1s, not an inline answer), quota cost and key requirement, and shared-state defaulting implied by the fresh parameter. These are exactly the operational traits an agent needs before invoking a non-idempotent, non-read-only call.

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 purpose and scope before constraints, and every sentence carries information (scope, exclusion, quota, key path, async flow). The quota/key sentence is dense but earns its place since an agent must know the call can fail on quota. Slightly telegraphic prose, but no 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?

No output schema exists, yet the description describes the answer's substance and the async retrieval path via get_answer, and the schema covers the replay/declared recording semantics for watch and observer. The gap is that ticket lifetime, polling expectations, or failure modes for a queued question are not stated, which matters for an async tool.

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?

Schema coverage is 75% and fresh/watch/observer are already documented in the schema, so the baseline would be 3. The description adds meaning to the required 'question' parameter, which is bare in the schema, by constraining it to live tracked coverage rather than general knowledge, which is a genuine semantic addition the schema lacks.

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 (ask) plus the exact resource and scope: what the tracked record shows about a named entity or unfolding event, and enumerates the answer content (what changed, current holdings, corroborating sources). It explicitly contrasts with generic Q&A and names the sibling get_answer as the collection step, so an agent can separate it from get_entity, get_record, or traverse.

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

Usage Guidelines5/5

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

Gives an explicit when-not ('Not general knowledge or history — grounding is live tracked coverage'), documents the rate limit (25/day per network address, then one Read per question on a free key obtained via POST /api/keys), and names the follow-up tool (get_answer). The condition for using it versus a plain knowledge source or an alternative sibling is clear.

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

All signal-bureau 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