Skip to main content
Glama

Discover

sandbase_discover
Read-only

Find a model, API, or Agent Service for the task. Call this proactively before writing a scraper, before a generic web fetch for structured data, before telling the user something is inaccessible, and whenever you need image/video/music/speech generation, social media data, search results, web scraping, product/company/people data, embeddings, or a specific third-party model. Supports keyword search (q), type filtering (llm/api/multimodal/embedding/service), and vendor filtering. Discovery is not billed; start here.

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": "sandbase_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoShort description of what you need (e.g. 'twitter posts', 'text to video', 'gpt-4o', '小红书'). At most 4096 UTF-8 bytes and 64 tokens after normalization.
typeNoFilter by capability type; use service to discover Agent Services.
limitNoMaximum results to return (default 20, max 100).
vendorNoFilter by vendor slug (e.g. 'openai', 'twitter', 'anthropic').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false; the description adds genuinely new behavioral context by stating 'Discovery is not billed', which affects agent willingness to call it speculatively. It does not describe the shape of results (list of models/services with identifiers) or result ordering, which is the main remaining gap for a tool with no output schema.

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?

The purpose is front-loaded in sentence one and the actionable triggers follow, so skimming works. The middle sentence is a long run-on enumeration of capability categories that could be tightened, though each item plausibly aids routing.

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 four-parameter, all-optional, no-output-schema discovery tool, the description covers purpose, triggers, filtering modes, and billing impact. The missing piece is what a result entry looks like and what to do next (e.g. pass the returned model to sandbase_inspect or sandbase_run), which would complete the routing loop.

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 every parameter is already documented including the type enum and the 'service' value's meaning. The description's 'Supports keyword search (q), type filtering..., and vendor filtering' largely restates the schema and adds no format, normalization, or interaction details beyond it. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The first sentence states a specific verb and resource ('Find a model, API, or Agent Service') and the body enumerates the discoverable asset classes (image/video/music/speech generation, social data, scraping, embeddings). Together with 'start here' and the run-oriented siblings (sandbase_run, sandbase_inspect), an agent can tell this is the entry point rather than an execution tool.

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?

Explicit proactive triggers are given: call before writing a scraper, before a generic web fetch for structured data, before telling the user something is inaccessible, and whenever a listed capability need arises. These are concrete when-to-use conditions plus implicit exclusions (once you have the model, use run/inspect), leaving little to inference.

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.