Skip to main content
Glama
Sign In
aqb-agent

aqb-agent

by yss787976-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

aqb_discover

Fetches an AQB discovery document from an agent host, letting clients locate the agent's settlement and identity endpoints before interacting with it.

Instructions

Fetch AQB discovery doc from an agent host

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": {
      "host": "<host>"
    },
    "name": "aqb_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only fetch, but does not disclose authentication requirements, network behavior, error handling, or what the discovery document contains.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though the undefined 'AQB' acronym reduces immediate clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one undocumented parameter, no annotations, and no output schema, the definition is too sparse to fully guide correct invocation. It identifies the action and source but omits host format, expected response, and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the single 'host' parameter. Saying 'from an agent host' clarifies that host identifies an agent host, but it does not specify whether it is a URL, hostname, DID, or another identifier format.

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 states a specific verb, 'Fetch', and a specific resource, 'AQB discovery doc', plus its source, 'from an agent host'. It is clear what the tool does, but it does not differentiate it from similarly named discovery-related siblings.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The agent must infer that this is a discovery step without any explicit context or prerequisites.

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

This server cannot be deployed

Other Tools