Skip to main content
Glama

Seahawk Media

Search Seahawk Media

ask
Read-onlyIdempotent

Search seahawkmedia.com: services, solutions, guides, best-of lists, articles, glossary terms and company pages. Returns the most relevant pages with title, URL and description, ranked. Ask in plain words, e.g. "wordpress maintenance plans" or "migrate from wix".

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat to look for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 real behavioral detail beyond that: results are ranked and each item carries title, URL and description, and the search is confined to seahawkmedia.com. It stops short of noting the 25-result cap or how ranking behaves.

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 sentences, front-loaded with purpose, then scope of results, then query style with examples. Every sentence earns its place and nothing is padding.

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 search tool with rich annotations and no output schema, the description covers what the tool searches, what it returns and how to phrase input. The only gap is the undocumented limit parameter and any result-cap behavior, which the schema's minimum/maximum partially mitigate.

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?

Schema coverage is only 50% — query has a terse "What to look for" and limit is undocumented. The description compensates meaningfully for the important parameter by telling the agent to ask in plain natural language and giving two worked examples, which clarifies expected input style beyond the schema. It says nothing about limit.

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?

Names a specific verb ("Search") and a concrete resource scope: seahawkmedia.com with an enumerated set of content types (services, solutions, guides, best-of lists, articles, glossary terms, company pages). That enumeration implicitly separates it from get_page (a single page fetch) and the site-checking siblings, though no sibling is named explicitly.

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?

Implies usage (find content on the site by describing it in plain words) and gives concrete query examples like "wordpress maintenance plans" and "migrate from wix". However it never states when to prefer get_page or get_company_overview instead, and gives no exclusions, so routing must be inferred from the sibling names alone.

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