Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

search_semantic

[$0.005] Search indexed news_intel and web_search articles by semantic meaning using local nomic-embed-text cosine similarity and persistent SQLite vector caching.

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_semantic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax semantic matches to return (default 5)
queryNoNatural-language semantic search query
sourceNoCorpus: 'all', 'news_intel', or 'web_search'all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the $0.005 cost, that embeddings are computed locally, and that vectors are persistently cached in SQLite, which hints at caching-related staleness/latency behavior. It says nothing about index freshness, rate limits, or what similarity information accompanies 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?

A single dense sentence with the price front-loaded and no filler. It reads slightly jargon-heavy (cosine similarity, SQLite vector caching) but every clause conveys real information.

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 3-parameter, fully documented read tool with no output schema, the description covers what is searched and how matching works. It omits what a result contains (similarity score, snippet, URL) and how current the vector index is, which an agent would want before ranking or citing results.

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 limit, query, and source are already fully documented, including the valid corpus values. The description only corroborates the two corpus names; it adds no syntax, scoring, or result-shaping detail beyond the schema, so baseline 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 (search), the exact corpora searched (news_intel and web_search), and the retrieval mechanism (nomic-embed-text cosine similarity). An agent can distinguish it from a generic 'search' or 'news' tool by the semantic-retrieval framing, though no sibling is named explicitly.

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: 'semantic meaning' suggests this is for conceptual/natural-language queries rather than keyword matching, and the two corpora scope where it applies. There is no explicit when-to-use/when-not guidance or named alternative for keyword or full-text lookups.

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.

Resources