Skip to main content
Glama

Little Works

get_seo_summary

Title, description, schema type, primary CTA verb, place, price.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
slugNo
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about read-only safety, authentication, failure modes, or what the response contains beyond a field list. 'Get' implies a read, but that is not stated or reinforced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but is a fragmentary noun list rather than a structured explanation. It lacks a leading purpose statement and leaves the agent to infer how the fields relate to inputs or outputs.

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?

For a three-parameter retrieval tool with no annotations and no output schema, the definition is far too thin. It gives a partial field list but omits parameter meaning, output framing, and usage context.

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

Parameters1/5

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

The schema has three parameters (url, slug, type) at 0% description coverage, and the description does not explain any of them. It lists what appear to be output fields instead, leaving input selection and precedence completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bare list of SEO fields (title, description, schema type, CTA verb, place, price) that implies what data the summary includes, but it never states the action or confirms it retrieves an SEO summary. The tool name supplies most of the purpose, and there is no differentiation from siblings such as get_listing_by_url.

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?

There is no when-to-use guidance, no mention of when not to use it, and no alternative tools named. An agent must infer all routing decisions from the tool name 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