Skip to main content
Glama
Sign In
mcp-server-apollo

mcp-server-apollo

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Apollo Capabilities

apollo_search_capabilities
Read-onlyIdempotent

Search Apollo MCP server capabilities and examples to identify the right tool for your data discovery task.

Instructions

Search the Apollo MCP server capabilities and examples. Use this first when deciding which Apollo tool to call.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds that it provides 'capabilities and examples', which is behavioral context beyond 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?

Two concise sentences that front-load purpose and usage. Every sentence adds value with no redundancy.

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?

No output schema, so description should clarify return structure. It mentions 'capabilities and examples' but not format. For a simple search tool, it is adequate but leaves some ambiguity.

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%. Description does not explain the two parameters (query and limit) beyond their schema types. With no explanation, an agent may not know how to use them effectively.

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?

Clearly states 'Search the Apollo MCP server capabilities and examples'. Differentiates from sibling tools by advising to use it first when deciding which tool to call.

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?

Explicitly says 'Use this first when deciding which Apollo tool to call', providing clear guidance on when to use. Does not explicitly exclude scenarios but context implies it is a discovery tool.

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

Deploy Server

Other Tools