Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

find_vocabulary

Read-only

The API vocabulary — thousands of resources, actions, personas, domains, schemas, and tags extracted from the API landscape. Filter by category.

Input Schema

NameRequiredDescriptionDefault
qNoFree text over title, summary, tags, and body.
pageNoPage number, 1-based (default 1). Use with `limit` to walk a long list.
sortNoOrder when there is no `q`: "default" (dated content newest first, the rest A-Z), "title" (A-Z) or "date" (newest first). A `q` always orders by relevance.
tagsNoTag slugs; match any by default.
limitNoResults per page, 1-100 (default 25).
matchNoHow multiple `tags` combine: "any" (default, at least one) or "all" (every tag).any
fieldsNoReturn only these keys on each record, e.g. ["slug","title","url"].
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.
categoryNoVocabulary category: resources, actions, personas, domains, schemas or tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Vocabulary category: resources, actions, personas, domains, schemas or tags."
    • addedInput schema / properties / fields / description
      Added value: +"Return only these keys on each record, e.g. [\"slug\",\"title\",\"url\"]."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / sort / description
      Added value: +"Order when there is no `q`: \"default\" (dated content newest first, the rest A-Z), \"title\" (A-Z) or \"date\" (newest first). A `q` always orders by relevance."
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-corpus behavior are covered structurally. The description adds useful framing that the vocabulary is extracted from the API landscape and is large ('thousands'), but says nothing about result shape, pagination limits beyond the schema, or the unusual side-channel role of the `context` parameter.

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?

Two short sentences, front-loaded with the resource definition and closed with the operative filter hint. No filler or redundancy; every clause carries information.

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 nine optional parameters, 100% schema coverage and no output schema, the structured fields do most of the work, so the terse prose is defensible. However, for a tool whose results are records drawn from a large taxonomy, the description never clarifies what a returned record contains or how this aggregate relates to the narrower find_* siblings, leaving a completeness 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?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents all nine parameters thoroughly (sort semantics, tag matching, pagination). The description's only parameter contribution is the category filter, which merely restates an enum already in the schema.

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 names the resource clearly (an API vocabulary of resources, actions, personas, domains, schemas, tags) and states it is filterable by category, so the agent knows exactly what corpus is behind `find_vocabulary`. It does not distinguish itself from siblings like `find_tags` or `find_entities`, which overlap with the 'tags' and other categories it mentions, leaving some ambiguity about when this aggregate tool wins.

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?

The closing phrase 'Filter by category' implies the primary retrieval pattern, but there is no explicit when-to-use or when-not-to-use guidance, nor any mention of the sibling find_* tools that cover narrower slices. Usage is inferable but not spelled out.

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

All api-evangelist toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources