Skip to main content
Glama

AstraNL Coordination Protocol

network_door

Read-onlyIdempotent

Classify a public HTTPS site using bounded, pinned publication reads. Publication is not measurement or purchase authority. No account, project or registry change. Read only. For a digest receipt of this read, confirmable through any door, call read_with_receipt.

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": {
      "site": "<site>"
    },
    "name": "network_door"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesBare public domain or HTTPS site origin, with no path or query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / receipt
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real semantic context beyond that: reads are "bounded" and "pinned", no account/project/registry state changes occur, and the publication carries no measurement or purchase authority — a meaningful limit on how results may be interpreted. It still leaves "bounded" and "pinned" undefined and says nothing about failure modes.

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?

Four short sentences, front-loaded with the core action followed by authority disclaimers and the sibling pointer. Minor waste in "No account, project or registry change. Read only." which restates the readOnlyHint annotation, and the domain vocabulary is denser than needed.

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 one simple parameter and full annotation coverage, the mechanics are adequately covered, but there is no output schema and the description never indicates what a classification result looks like. For a tool whose entire value is a classification verdict, that is a noticeable gap.

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?

There is a single parameter with 100% schema coverage, including a clear constraint (bare public domain or HTTPS origin, no path or query). The description only echoes "public HTTPS site" and adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 names a verb and resource ("Classify a public HTTPS site") but the outcome is never made concrete — what a classification contains or is used for is left to jargon like "bounded, pinned publication reads" and "publication is not measurement or purchase authority". It does distinguish itself from read_with_receipt, but an agent still cannot confidently say what this tool produces.

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?

One explicit routing rule is given: for a digest receipt of this read, call read_with_receipt. Beyond that there is no guidance on when classification is the right move versus the many siblings (check_counterparty_nl, find_offers, check_material), and no stated prerequisites or exclusions.

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