Skip to main content
Glama

search_suprsend_documentation

Read-onlyDestructiveIdempotent

Search SuprSend product documentation to find technical guidance on APIs, SDKs, workflows, templates, tenants, lists, vendors, and connectors. Use precise queries for accurate snippets.

Instructions

Search SuprSend's product documentation for technical guidance — APIs, SDKs, workflows, templates, tenants, lists, vendors, and connectors.

When to use:

  • The user asks how a SuprSend feature works or how to integrate one.

  • You need to verify a behavior before calling a write tool.

  • You're debugging an integration error.

When NOT to use: for runtime operations on SuprSend resources (users, objects, tenants, workflows) — those have dedicated tools.

Returns: a JSON array of {uri, snippet}. Snippets are excerpts; if a snippet doesn't fully answer, follow up with fetch_suprsend_documentation on the relevant uri.

Tips: use precise technical terms ("workflow trigger conditions", not "the rule thing"); add synonyms if the first query returns nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query. The query should: - Identify the core concepts and intent - Add relevant synonyms and related terms - Structure the query to emphasize key terms - Include technical or domain-specific terminology if applicable
Behavior2/5

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

The description adds return format details but contradicts annotations: it implies read-only search, yet annotations set destructiveHint=true. No mention of side effects, rate limits, or other behaviors beyond return format.

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

Conciseness5/5

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

Description is well-structured with sections and bullet points, front-loads purpose, and every sentence adds value. No wasted words.

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?

Given no output schema, description explains return format and suggests follow-up with fetch_suprsend_documentation. Covers usage contexts adequately for a search tool. Missing info on pagination or limits, but acceptable.

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?

Input schema covers the query parameter with detailed description (100% coverage). Description adds a tip about synonyms, but adds minimal extra meaning beyond schema.

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 description clearly states the tool searches SuprSend's product documentation for technical guidance, listing specific topics like APIs, SDKs, workflows, etc. It distinguishes from runtime operation tools, making purpose very specific.

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 'When to use' and 'When NOT to use' sections provide clear context and alternatives, such as using dedicated tools for runtime operations. Includes tips for effective querying.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suprsend/cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server