Skip to main content
Glama
Sign In

docs

by com.politicalcomms
OverviewDiscussionsAdmin

Search documentation

search_political_comms
Read-onlyIdempotent

Search across the Political Comms knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Political Comms, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to head or cat the page path (append .mdx to the path returned from search — e.g. a result at /some/page is read with head -200 /some/page.mdx).

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the description is free to add the valuable parts: the return shape ('contextual content with titles and direct links') and a concrete follow-up recipe (append .mdx, read with head/cat via the sibling tool). It does not mention result counts, ranking behavior, or pagination limits, which keeps it below a 5.

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?

Four sentences, front-loaded with purpose and use cases before the follow-up workflow, and no filler. The .mdx/head example is long but earns its place as an actionable instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing what comes back and how to chain into the sibling tool for full page content. For a one-parameter, read-only search tool this gives an agent everything needed to call it correctly and act on 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% for the single parameter, so baseline is 3, but the schema text is only 'Search query' and the description adds no guidance on phrasing (natural language vs. keywords, quote syntax, scope). The parameter is adequately but thinly documented.

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 across the Political Comms knowledge base') and enumerates the content types returned (info, code examples, API references, guides). It is clearly distinguishable from query_docs_filesystem_political_comms, which it positions as the raw-file reader.

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?

Gives concrete triggering conditions ('answer questions about Political Comms, find specific documentation, understand how features work, locate implementation details') and explicitly routes the agent to an alternative when full page content is needed. Both the when-to-use and the when-to-use-something-else are covered.

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

All docs toolsInspect
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