Skip to main content
Glama

About catchy-me

catchy_info
Read-onlyIdempotent

What catchy-me is and how it works: lead search with facts and AI outreach, plans, briefs and credits, how to connect this MCP server (OAuth or an API key), how an agent signs up by itself, and the links to the Terms of Use and the Privacy Policy. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: the response includes connection instructions for OAuth vs API key, self-signup flow, and legal-document links, and it works without sign-in. That extra context fills in what the call returns and the prerequisites, which is the right contribution given the annotations.

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?

Two sentences: a front-loaded colon-list of covered topics, then the sign-in constraint. The list is dense and each item maps to a real thing an agent might need. Slightly list-heavy but no filler sentences.

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?

With no output schema, the description must convey the return content, and it does so by enumerating the topics covered. Combined with zero parameters and rich read-only annotations, an agent has enough to call it correctly. Only a explicit routing statement ('call before authenticating') is absent.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter-level meaning is required or missing.

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?

The description states a specific content scope — what catchy-me is, how lead search/AI outreach work, plans/briefs/credits, MCP connection via OAuth or API key, agent self-signup, and legal links. An agent can distinguish it from siblings like get_account or accept_legal because it is explicitly the product/onboarding overview. It is content-led rather than verb-led ('What catchy-me is...'), which keeps it just 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?

The closing 'No sign-in needed' implies this is safe to call before authentication, which is real usage signal. However, it never says explicitly 'call this first' or 'use this instead of get_account when you need orientation', so the when-to-use decision is left to inference from the topic list.

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