Skip to main content
Glama

SubscriptionFlow

Search SubscriptionFlow knowledge

search
Read-only

Search the published SubscriptionFlow knowledge base by free-text query. Returns matching articles with ids you can pass to fetch. Only published content is searchable. Public, read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-50.
queryYesFree-text search query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so safety is covered. The description adds genuine behavioral context beyond that: only published content is indexed, the service is public, and results include ids that feed `fetch`. It says nothing about result ranking or empty-result behavior, but the bar is lower given annotations.

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?

Four short sentences, front-loaded with purpose, then the return contract, then the indexing constraint, then the access model. No filler or redundant restatement of the tool name.

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 simple two-parameter read-only search with no output schema, the description covers purpose, scope limits, access model, and the downstream handoff to `fetch`. Only ranking/pagination behavior is unaddressed, which is minor for this tool class.

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 description coverage is 100%, with query and limit both documented inline, so baseline 3 applies. The description restates free-text querying but adds no syntax, operators, or limit behavior beyond the 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?

States a specific verb and resource (search the published SubscriptionFlow knowledge base) and scopes it to free-text queries. It also distinguishes itself from the sibling `fetch` by saying results carry ids intended for that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context: search the knowledge base by free text, then hand ids to `fetch`. The 'only published content is searchable' line signals when results may be incomplete. It stops short of explicit when-not guidance or naming other siblings like sf_contact for non-article questions.

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