Skip to main content
Glama
Sign In

rankoracle

by io.tooloracle
OverviewDiscussionsAdmin

title_optimizer

Analyze current title tag and generate SEO-optimized title suggestions

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to fetch current title from (optional)
keywordNoTarget keyword
draft_titleNoYour current title (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It says it analyzes a current title tag but doesn't disclose how it obtains that title (URL fetch vs draft input), whether the operation is safe/read-only, or what occurs if neither url nor draft_title is provided. This ambiguity is significant given the lack of structured 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?

The description is a single, front-loaded sentence that efficiently captures the tool's core function. However, it omits some behavioral details, which slightly detracts from its completeness, but as a concise statement it is well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, the description should clarify return values and input requirements. It doesn't mention whether at least one of url or draft_title is needed, nor the format of the suggestions. This under-specification limits its contextual completeness for an agent.

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?

The input schema includes descriptions for all three parameters (url, keyword, draft_title), achieving 100% schema coverage. The description adds no additional parameter semantics, so a baseline score of 3 is appropriate.

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 uses specific verbs 'Analyze' and 'generate' with resource 'title tag' and 'title suggestions', clearly indicating it evaluates existing titles and produces optimized alternatives. While it doesn't explicitly name sibling tools, its focus on title tags distinguishes it from related tools like meta_generator or heading_analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only states the tool's function, leaving the agent to infer appropriate usage.

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

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