Skip to main content
Glama
Sign In

Agentic Web Wiki — standards reference, probe, validate, template

by wiki.agenticweb
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Search 132 standards and 52 glossary terms by keyword, acronym, alias, or 'A vs B' pair (pass q or alias query, 2–200 chars). Returns { results (top 10 ranked by title/alias/body match), matching_terms, comparison_url } or nearest_ids hints when empty. Use search for keyword discovery; use get for an exact id or ask for stack recommendations.

Input Schema

NameRequiredDescriptionDefault
qNosearch query or comparison (e.g. agent discovery, A2A vs MCP, accept payments)
queryNoalias for q: search query or comparison

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / q / description
      Added value: +"search query or comparison (e.g. agent discovery, A2A vs MCP, accept payments)"
    • addedInput schema / properties / query / description
      Added value: +"alias for q: search query or comparison"
  2. Changed2 schema fields changed
    • addedInput schema / properties / query
      Added value: +{
+  "maxLength": 200,
+  "minLength": 2,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "q"
-]
  3. Changed1 schema field changed
    • changedInput schema / properties / q / maxLength
      Previous value: -80New value: +200
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. Beyond that, the description adds meaningful behavioral detail: top 10 ranking by title/alias/body match, returned fields, and nearest_ids hints when no results are found.

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 dense sentences with no filler. The core search scope and return behavior are front-loaded, and the sibling-routing guidance follows immediately.

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?

Although there is no output schema, the description explains the response shape, ranking behavior, and empty-result fallback. For a search tool, this is complete enough for an agent to invoke it correctly.

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 coverage is 100%, so q and query are already documented, including their alias relationship and 2–200 character bounds. The description reinforces that either q or its alias query should be passed, but adds little beyond the schema.

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 set: search 132 standards and 52 glossary terms. It also names the supported query modes (keyword, acronym, alias, 'A vs B' pair) and distinguishes the tool from get and ask.

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 to use search for keyword discovery, get for an exact id, and ask for stack recommendations. This directly routes the agent among siblings with clear conditions.

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

All Agentic Web Wiki — standards reference, probe, validate, template 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