Skip to main content
Glama

Search the verified catalog

search_catalog
Read-onlyIdempotent

List the verified resources of the BOTERNITY catalog: exact extracts of specifications (MCP, HTTP, OpenAPI, robots.txt) with their source. The catalog is small and grows from requests.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoFilter by topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the catalog is small (so a full listing is cheap and likely unpaginated) and it grows from requests (so absence from results doesn't mean the resource doesn't exist). It does not say what the result rows look like or whether there is a limit.

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?

Two short sentences, front-loaded with the verb and the catalog scope; the parenthetical resource list is informative rather than filler. The closing sentence about the catalog being small is slightly tangential in position but earns its place.

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?

For a one-optional-param read tool with full annotations and no output schema, the definition covers purpose and rough content of results. It still leaves the relationship to read_catalog_resource and the shape of the returned list unspecified, which is a real gap for an agent choosing among catalog tools.

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% and the single optional 'topic' parameter is already documented with an enum in the schema. The description adds nothing about how topic filtering narrows results, but with full schema coverage the baseline of 3 applies.

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 (List) and a specific resource (verified resources of the BOTERNITY catalog) and clarifies the resource types inside (MCP, HTTP, OpenAPI, robots.txt extracts with source). It does not, however, differentiate itself from the sibling read_catalog_resource, so an agent can't tell from the description alone which of the two to call first.

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?

Usage is only implied: 'List the verified resources' suggests a browse/discovery step, and 'The catalog is small and grows from requests' hints that items can be obtained via request_resource when absent. Neither the follow-up tool (read_catalog_resource) nor the condition for requesting a missing resource is stated explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.