SuperPost

Search sources

search_sources

Read-onlyIdempotent

Searches relevant excerpts from the account's permitted sources. This read-only operation does not change or publish data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_sources"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`kind`	Yes
`items`	Yes
`query`	Yes
`notice`	No
`searchMode`	No
`authorUtterances`	Yes
`searchFallbackReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / items / items / properties / sourceScopeIds

Added value: +{
+  "items": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

First observedNov 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the sentence "This read-only operation does not change or publish data" largely restates what is already structured. The one bit of added value is the phrase "account's permitted sources," hinting that results are permission-scoped. Nothing is disclosed about ranking, result count behavior, or excerpt provenance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the useful clause. However, the second of only two sentences is almost entirely redundant with the readOnlyHint/destructiveHint annotations, so roughly half the text does not earn its place.

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?

The tool is simple (two params, output schema present so return shape needn't be explained) and the description covers the core action and scope adequately. What is missing — query semantics and the meaning of limit — is real but modest given the tool's low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so neither `query` (string, 1-500 chars) nor `limit` (integer, 1-20, default 8) is documented anywhere. The description provides no guidance on query form (natural language vs. keywords), how limit affects results, or what happens at the maximum. With low coverage the description should compensate, and it does not.

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?

"Searches relevant excerpts from the account's permitted sources" gives a specific verb (searches) and a specific resource (source excerpts), which is distinguishable from siblings like get_source_transcription or read_source_file. It stops short of explicitly naming those siblings as alternatives, so it falls short of a 5.

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: an agent can infer this is the tool for finding relevant content across sources rather than retrieving a specific known file. There is no explicit when-to-use statement, no exclusion against read_source_file / get_source_transcription, and no mention of prerequisites such as needing configured source scopes.

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

All SuperPost tools Inspect

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

Need Help?