signal-bureau

get_entity

Read-onlyIdempotent

Full dossier for one entity: its canonical identity (canonicalId sb:e/... is durable and equals the traverse node id; slug is a discovery input and may change; aliases; addresses for the page, the node door and MCP), self-describing counts — counts.attention.current (documents and coverage verticals on the detection day, scope tracked-coverage) and counts.evidence.total (documents and publishers over firstSeen..lastSeen, scope retained-corpus), each with unit, window and scope, and a window that cannot be determined says cannot-measure — plus trajectory, source-attributed evidence, observed home categories, and why it's surfacing. The bare signals/verticals keys are deprecated aliases of counts.attention.current. Not found returns found:false with the identity rule.

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>"
    },
    "name": "get_entity"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description adds real behavior: canonicalId is durable vs slug which may change, counts carry unit/window/scope with 'cannot-measure' when a window is indeterminate, deprecated alias keys, and a found:false not-found response with the identity rule. It does not mention auth or pagination, keeping it out of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading is good ('Full dossier for one entity'), but the remainder is a single dense run-on packed with internal jargon (counts.attention.current, scope retained-corpus, coverage verticals) that is hard to parse in one pass. The content is mostly relevant, but the structure does not let an agent scan it efficiently.

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 voluntarily specifies the return shape (identity, dual counts with units/windows/scopes, trajectory, evidence, categories) and the not-found case, which is strong coverage for a read-only lookup. The remaining gap is the unresolved 'name' input semantics.

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?

The schema has 0% description coverage on the single 'name' parameter, so the description must carry it. It discusses the identity model (canonicalId sb:e/..., slug, aliases, addresses) but never states which of these the 'name' argument accepts, leaving invocation ambiguous even though it adds useful identity context.

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?

Opens with a specific verb+resource: 'Full dossier for one entity', and enumerates the payload (identity, counts, trajectory, evidence, categories). It also anchors itself against the sibling 'traverse' by stating the canonicalId equals the traverse node id, though it never names search_entities as the discovery counterpart it is implicitly paired with.

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?

There is no explicit when-to-use or when-not-to-use statement against siblings like search_entities, traverse, or get_topic_record. The only implied routing is the remark that 'slug is a discovery input', which hints at a discover-then-fetch flow, but the agent must infer it.

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

All signal-bureau tools Inspect

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

Need Help?