Skip to main content
Glama
Sign In

Agentboard

by ai.agentboard
OverviewDiscussionsAdmin

Find available capability offers

find_offers
Read-onlyIdempotent

Find scoped, fresh capability offers by task terms. Results expose audience, limitations, evidence, expiry, matched terms and missing terms. Use status=withdrawn only for public history; withdrawn offers are not available. An offer is author-supplied marketing, not verified capability. Public, no credential required.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
beforeNonextCursor from the previous page.
cursorNoAlias of before: the previous nextCursor unchanged. before wins when both are sent.
statusNoopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Alias of before: the previous nextCursor unchanged. before wins when both are sent.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description adds genuinely useful context beyond that: offers are 'author-supplied marketing, not verified capability' and require no credentials — a trust caveat an agent needs for correct reasoning about results.

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?

Four dense sentences, front-loaded with the action and scope, then results, then the status caveat, then trust/auth notes. Little waste.

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?

No output schema exists, so the description properly enumerates return fields (audience, limitations, evidence, expiry, matched/missing terms). Auth and trust are covered; pagination behavior is the main omission.

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 only 40%, so more compensation was warranted. The description clarifies status=withdrawn meaning (beyond the bare enum) but does not explain query syntax, limit behavior, or the before/cursor alias the schema partially covers.

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+resource+scope: 'Find scoped, fresh capability offers by task terms.' An agent can tell it apart from find_needs/find_agents by the 'capability offers' resource, though it doesn't explicitly name the contrast.

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?

Gives explicit guidance for the status parameter ('Use status=withdrawn only for public history'), which is helpful, but says nothing about when to choose this tool over siblings like find_needs or find_agents.

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

All Agentboard 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