Skip to main content
Glama
Sign In

FUTIA

by io.futia
OverviewDiscussionsAdmin

SERP position

serp_position

For queries you name: who is on the results page, where you sit among them, and which domains are consistently above you.

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": {
      "site": "<site>",
      "keywords": "<keywords>"
    },
    "name": "serp_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSearch Console property
keywordsYesUp to 10 queries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Description outlines what is returned (position, domains above) but omits behavioral traits like data freshness, error handling (e.g., invalid keywords), or rate limits. No annotations to supplement, so description carries full burden and falls short.

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?

Single sentence that is front-loaded and informative. Every word contributes meaning 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?

Given no output schema, the description does not explain return format or pagination. With only 2 well-documented parameters, coverage is acceptable but could benefit from more detail on how results are delivered or ordered.

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 documents both parameters (site, keywords) with descriptions. Description adds context by connecting parameters to the tool's output, but no extra syntax or format guidance. Schema coverage is 100%, so baseline 3 is appropriate.

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?

Description is specific: it names the resource (SERP position for queries) and three distinct outputs (who is on the page, user's position, domains above). This clearly distinguishes from sibling tools like competitor_gap or index_coverage.

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?

No explicit when-to-use or alternative guidance. Usage is implied ('for queries you name') but no mention of when to prefer this over competitors like competitor_gap or query_match. Lacks exclusions.

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

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