APAC Licensed-Entity Lookup

by dev.workers.regnotes.apac-license-lookup

get_licensed_entity

Read-only

Full register record for one entity id from search_licensed_entities, with source URL, as-of date and other registrations. Not legal advice. Costs $0.02 USDC on Base via x402.

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": {
      "id": "<id>"
    },
    "name": "get_licensed_entity"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark this read-only and closed-world; the description adds genuinely new context the annotations don't carry: the paid nature ($0.02 USDC on Base via x402), the returned fields (source URL, as-of date, other registrations), and a legal disclaimer. It does not contradict openWorldHint=false.

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

Conciseness5/5

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

Three tight sentences front-loaded with purpose, then provenance of the id, then cost and return contents; every clause earns its place.

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?

Covers what the record contains, where the id comes from, and the payment cost, which is sufficient for a single-parameter lookup without an output schema. Minor gap: no note on failed lookups or what 'other registrations' includes.

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 description coverage is 0% with a single 'id' string parameter, but the description compensates by specifying the id is an entity id sourced from search_licensed_entities, which is the one piece of semantics an agent needs.

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 and resource ('Full register record for one entity id') and identifies the sibling tool that produces the id, so the agent can distinguish it from search_licensed_entities without opening either schema.

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

Usage Guidelines4/5

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

Explicitly directs the agent to obtain the id from search_licensed_entities, establishing the natural call order. It lacks an explicit 'do not use for X' exclusion, but the retrieval-after-search flow is clear.

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

All APAC Licensed-Entity Lookup 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?