Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

lookup_syndicate_dossier

Looks up an indicted threat-group dossier when Protocol AO-061 public release is enabled or caller holds operator authorization.

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": {
      "dossier_id": "<dossier_id>"
    },
    "name": "lookup_syndicate_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
dossier_idYese.g. DF-SYN-01 or DF-SYN-ABCD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a real behavioral trait beyond the schema — an access-control gate tied to a protocol flag or operator authorization — which is genuinely helpful. However, it says nothing about what happens when the gate fails (error vs. empty result) or what the dossier contains, leaving substantial disclosure gaps for an unannotated tool.

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?

A single sentence with no filler, and the resource being looked up is front-loaded ahead of the conditional access clause. The trailing 'when...' clause is slightly dense but every part of it carries meaning.

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?

For a one-parameter, unannotated, output-schema-less tool, the description covers what is retrieved and the authorization gate, which is the most important thing an agent needs. It stops short of describing the returned dossier's shape or the failure behavior, which matters here because there are no annotations or output schema to fall back on.

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 100% and the single parameter carries an example format (DF-SYN-01 or DF-SYN-ABCD) in the schema itself, so the schema already does the work. The description adds no parameter detail but also needs to add none; with only one well-documented required parameter, this is close to the 0-param baseline of 4.

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?

The description names a specific verb ('looks up') and a specific resource ('an indicted threat-group dossier'), so an agent knows exactly what kind of record is retrieved. It does not differentiate from any sibling, but no sibling in the supplied list appears to overlap, so the gap is minor.

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?

It states a precondition for use: Protocol AO-061 public release must be enabled, or the caller must hold operator authorization. That is useful gating information, but it is framed as an access condition rather than a when-to-use/when-not-to-use rule, and no alternative tool or fallback path is offered for callers who fail the gate.

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