Azquo

Look up names and notes

describe_query

Read-only

Resolve a name-query expression and return the matched names with full details: parents, attributes (including AI Text bodies and any other attribute values), and child counts.

The query is a name expression as understood by the Azquo NameQueryParser. Common forms:

An exact display name (e.g. "State + Territory derivation")
A set verb in POSTFIX position after a backtick-quoted name: API endpoints children Florida Coverages parents Sales from 2024 to 2025 Set verbs are ALWAYS postfix. The prefix English form "children of X" is NOT valid AQL — the parser will try to resolve "of" as a name and fail.
Set algebra on backtick-quoted names: Florida * Coverages (intersection), A + B (union), A - B (difference)

Read-only: "edit:..." commands and "... as " assignments change the database, so they are refused here - run them through aql_write. A name containing the word "as" must be in backticks.

Use this after list_names / describe_set to read attribute values that the other discovery tools don't surface — most importantly the AI Text attribute on a note. Internal/user storage attributes are filtered out by the server.

Each resolved entry includes its integer id — use it directly to chain into edit_name_attributes or delete_name without a separate lookup.

Limit defaults to 50 resolved names per call.

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": {
      "database": "<database>",
      "query": "<query>"
    },
    "name": "describe_query"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max resolved names to return (default: 50)
`query`	Yes	Name-query expression. Postfix set verbs only — `Topic` children, NOT `children of Topic`.
`business`	No	Optional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.
`database`	Yes	Database name

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / business

Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses that 'edit:...' commands and '... as <set>' assignments are refused because they mutate, that internal/user storage attributes are server-filtered, and that limit defaults to 50. These are concrete behavioral traits not present in the annotations.

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-loaded with purpose and return shape, then structured bullets for query syntax and behavioral notes. It is long, but for a query-language tool the syntax guidance and examples each earn their place; only minor trimming is possible.

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

Completeness5/5

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

No output schema exists, so the description correctly documents the return shape (parents, attributes, AI Text bodies, child counts, integer id). Combined with the syntax rules, write-refusal, attribute filtering, and default limit, an agent has everything needed to call and chain it.

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%, but the description goes well beyond it for the key 'query' param: postfix set-verb syntax, the backtick-quoting rule (including names containing 'as'), and set algebra operators (*, +, -) with examples. It adds little for 'business'/'database', so not a full 5.

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 (resolve) and resource (name-query expression) and enumerates the return payload: matched names with parents, attributes including AI Text bodies, and child counts. It explicitly distinguishes itself from sibling discovery tools (list_names, describe_set) and from the write path (aql_write, edit_name_attributes, delete_name).

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?

Explicitly says when to use it: 'Use this after list_names / describe_set to read attribute values that the other discovery tools don't surface.' It also routes write commands to aql_write and explains how to chain the returned id into edit_name_attributes or delete_name, covering when-not and alternatives.

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

All Azquo 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?