Skip to main content
Glama

Agent Discovery Board by SarnAI

by dev.sarnai
OverviewDiscussionsAdmin

Describe a listing

describe_listing
Read-onlyIdempotent

Everything needed to use one listing: how_to_connect steps per connection, each with a call recipe (method, headers, inputs, an example where known; gaps are listed, never guessed), a payment summary, whether it has a verification template, and trust signals (stale, source, claimed, last health check and its age). 404 unknown_listing. Free.

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional label for yourself (statistics only).
trace_idNoFrom a previous response, to continue it; omit on the first call.
listing_idYesListing id (UUID), e.g. from find_agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / listing_id / description
      Previous value: -"A listing id (UUID), e.g. from find_agents."New value: +"Listing id (UUID), e.g. from find_agents."
    • 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. Changed5 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 / trace_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / trace_id / type
      Added value: +"string"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description is free to add real value — and it does: the 404 unknown_listing failure mode, cost ('Free'), and the honesty guarantee that recipe gaps are 'listed, never guessed'. It does not cover rate limits or payload size, but the added context is well beyond the structured fields.

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?

Front-loaded with the core promise, then a tight enumerated list of return contents, closing with error and cost. The middle parenthetical about recipes is dense but each clause carries distinct information; nothing is padding.

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?

With no output schema, the description correctly takes on the burden of describing return contents in detail, plus the error case and pricing — everything an agent needs to call it and interpret the result. The only gap is its unresolved relationship to get_listing.

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%, including a concrete UUID example for listing_id, so the schema carries parameter meaning. The description adds nothing about listing_id format or how trace_id continuation interacts with this call, leaving it at the baseline for well-documented schemas.

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?

States a specific verb and resource and enumerates exactly what the response contains (connection recipes, payment summary, template flag, trust signals), so an agent knows what it gets. However, it never distinguishes itself from the sibling get_listing, leaving a real ambiguity about which 'fetch one listing' tool to pick.

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 phrase 'Everything needed to use one listing' implies the use case (deciding whether/how to connect to a listing), but there is no explicit when-to-use, no when-not-to-use, and no pointer to get_listing or find_agents as alternatives. Usage is inferable rather than stated.

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