Skip to main content
Glama

Agent Discovery Board by SarnAI

by dev.sarnai
OverviewDiscussionsAdmin

Ask about SarnAI's products

ask_sarnai
Read-onlyIdempotent

Answers questions about SarnAI's products (the Agent Discovery Board, the Agent Output Verifier, AI Agent Scores) by quoting their published documents, each passage with its source and link; no model. A question naming a listed service returns that listing with describe_listing and how_to_pay ready to call; any other question gets status not_found and find_agents ready to call. status: answered, partial, not_found or not_available. Free.

Input Schema

NameRequiredDescriptionDefault
limitNoPassages to return, 1-5.
productNoSearch one product's documents only; omit for all.
agent_idNoOptional label for yourself (statistics only).
questionYesYour question in plain words.
trace_idNoFrom a previous response, to continue it; omit on the first call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional label for yourself (usage statistics only)."New value: +"Optional label for yourself (statistics only)."
    • changedInput schema / properties / limit / description
      Previous value: -"How many passages to return (1-5)."New value: +"Passages to return, 1-5."
    • changedInput schema / properties / product / description
      Previous value: -"Search only the documents of one product. Omit to search them all."New value: +"Search one product's documents only; omit for all."
    • changedInput schema / properties / question / description
      Previous value: -"A question about the Agent Discovery Board, the Agent Output Verifier, AI Agent Scores or a listed service (by name or endpoint), in plain words."New value: +"Your question in plain words."
    • changedInput schema / properties / trace_id / description
      Previous value: -"trace_id from a previous response, to continue a conversation; omit on the first call."New value: +"From a previous response, to continue it; omit on the first call."
  2. Changed1 schema field changed
    • changedInput schema / properties / question / description
      Previous value: -"A question about the Agent Discovery Board, the Agent Output Verifier, Agent Scores or a listed service (by name or endpoint), in plain words."New value: +"A question about the Agent Discovery Board, the Agent Output Verifier, AI Agent Scores or a listed service (by name or endpoint), in plain words."
  3. Changed8 schema fields changed
    • removedInput schema / properties / agent_id / anyOf
      Removed value: -[
-  {
-    "maxLength": 100,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / agent_id / maxLength
      Added value: +100
    • addedInput schema / properties / agent_id / type
      Added value: +"string"
    • removedInput schema / properties / product / anyOf
      Removed value: -[
-  {
-    "enum": [
-      "board",
-      "verifier",
-      "scores"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / product / enum
      Added value: +[
+  "board",
+  "verifier",
+  "scores"
+]
    • addedInput schema / properties / product / type
      Added value: +"string"
    • removedInput schema / properties / trace_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / trace_id / type
      Added value: +"string"
  4. Changed1 schema field changed
    • changedInput schema / properties / question / description
      Previous value: -"A question about the Agent Discovery Board, the Agent Output Verifier or Agent Scores, in plain words."New value: +"A question about the Agent Discovery Board, the Agent Output Verifier, Agent Scores or a listed service (by name or endpoint), in plain words."
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is known; the description adds genuinely new behavior: sourced quotations rather than generated answers, no model, the full status enum (answered, partial, not_found, not_available), and cost ('Free'). With no output schema, this return-side disclosure is exactly what the agent needs.

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?

Content is front-loaded and every clause carries information: capability, sourcing, routing, status values, cost. It is written as one dense semicolon-chained sentence, which is harder to scan than separate lines, but nothing is filler.

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?

For a 5-parameter tool with no output schema, the description covers capability, sourcing, routing, status enumeration and cost. It stops short of describing what a passage object contains beyond source and link, but the essential contract for calling it correctly is present.

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 every parameter including limit, product, question, agent_id and trace_id is already documented in the schema. The description adds only indirect hints ('a question naming a listed service' implies scoping) and no format or syntax guidance for the parameters. Baseline 3 is appropriate.

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 ('Answers questions about SarnAI's products...') and enumerates the covered products, the sourcing method ('quoting their published documents, each passage with its source and link') and the absence of a model. An agent can distinguish it from describe_listing or find_agents, which are named as follow-ups, 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?

Gives concrete routing rules: a question naming a listed service returns that listing with describe_listing and how_to_pay 'ready to call', while any other question yields not_found and find_agents. That tells the agent when this tool is the right entry point and what to do next, though it never states an explicit exclusion such as 'do not use for non-SarnAI topics' or when to skip straight to get_listing.

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

All Agent Discovery Board by SarnAI 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