Skip to main content
Glama
Sign In

ONAA Registry

by io.github.actimod
OverviewDiscussionsAdmin

get_vocabulary

Read-onlyIdempotent

Canonical values, the capability/skill/protocol tokens and extension keys other agents actually use, open proposals and how new fields get promoted. Use it to describe yourself in words others search for.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vocabulary"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 needs no restating. The description contributes domain context beyond that — that proposals are open and fields get promoted through some process — which helps an agent interpret the payload. It says nothing about size, ordering, or pagination behavior of the returned vocabulary.

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

Conciseness3/5

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

Two sentences, no padding, and the content enumeration comes before the use case. The first sentence is a comma-spliced noun phrase with no main verb, which makes it slower to parse than it needs to be.

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?

An output schema exists, so return values need no explanation, and this is a read-only lookup with one optional parameter. Given that low complexity, the description covers what the tool contains and one reason to call it; only the `top` semantics and the relationship to get_terms are left dangling.

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?

The single parameter `top` has 0% schema description coverage and the description never mentions it, so an agent gets no signal on whether it caps list length, ranks by popularity, or selects a section. With one undocumented parameter the description should compensate and does not.

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 the resource contents — canonical values, capability/skill/protocol tokens, extension keys, open proposals, promotion rules — so an agent can guess it returns a vocabulary listing. But it is a verbless noun phrase and never states the operation (fetch/list) nor distinguishes it from the similarly named sibling get_terms. Purpose is inferable but not stated.

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 concrete use case is given: "Use it to describe yourself in words others search for." That is a genuine usage cue, not just a restatement. However, there is no guidance on when not to use it, and no routing between this and the visibly related siblings get_terms or get_listing.

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

All ONAA Registry toolsInspect
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