Skip to main content
Glama
Sign In

Miraqo

by io.github.deleteweb
OverviewDiscussionsAdmin

get_keyword_gap

Keyword gap dai competitor: keyword per cui un competitor si posiziona, con volume, posizione, difficulty, cpc e URL. only_uncovered=true (default) mostra solo quelle che il progetto NON copre. Paginato (max 100).

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": {
      "project_id": "<project_id>"
    },
    "name": "get_keyword_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
project_idYesID progetto (da list_projects)
competitor_idNoID da get_competitors; omesso = tutti
location_codeNomercato dello snapshot gap; omesso = mercato del progetto. Altri mercati esistono solo se già analizzati dalla pagina Competitor.
only_uncoveredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination (max 100), the default of only_uncovered, and the data returned. However, it does not mention whether the operation is read-only, any authentication requirements, or error conditions. The disclosure is adequate but not exhaustive.

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?

The description is concise and front-loaded, starting with the core purpose and then detailing the key parameter and pagination. Every sentence adds information without unnecessary fluff.

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 tool with 6 parameters, no output schema, and no annotations, the description covers the essential aspects: the returned fields, the key parameter behavior, and pagination. It does not elaborate on error handling or edge cases, but for a straightforward retrieval tool, it is sufficiently complete.

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 50% (3/6 parameters have descriptions). The description adds value for only_uncovered by explaining its default and effect, but it does not clarify limit, offset, or location_code beyond the schema. The provided information is helpful but not fully compensating for the coverage gap.

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 clearly states the tool retrieves keyword gaps from competitors, listing the returned fields (volume, position, difficulty, CPC, URL). It implies a distinction from get_keywords by specifying 'gap' and 'competitor', though it does not explicitly name a sibling. The purpose is unambiguous and specific.

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 description implies usage for competitor keyword analysis and explains the default behavior of only_uncovered, but it does not explicitly state when to use this tool versus alternatives like get_keywords or get_competitors. No exclusions or alternative routing are provided.

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

All Miraqo 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