Skip to main content
Glama

get_on_page_seo_guide

Access the Open Strategy Partners On-Page SEO Optimization Guide to implement SEO best practices for technical content and product positioning.

Instructions

Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_on_page_seo_guide' tool. It reads the content of 'on-page-seo-guide.md' from the script directory and returns it wrapped in a success dict, or an error if the file is missing. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    async def get_on_page_seo_guide() -> dict:
        """Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide."""
        script_dir = os.path.dirname(os.path.abspath(__file__))
        try:
            with open(os.path.join(script_dir, 'on-page-seo-guide.md'), 'r') as f:
                content = f.read()
                return {
                    "success": True,
                    "data": {
                        "content": content
                    }
                }
        except FileNotFoundError:
            return {
                "success": False,
                "error": "Required file 'on-page-seo-guide.md' not found in script directory"
            }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves—e.g., whether it returns a static document, requires authentication, has rate limits, or provides real-time data. This leaves critical behavioral traits unspecified.

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?

The description is a single, efficient sentence that directly states the tool's purpose with no unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It tells the agent what resource is retrieved but lacks context about the guide's format, update frequency, or how it differs from sibling tools. For a retrieval tool with no behavioral annotations, more detail would be helpful.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. A baseline of 4 is applied for zero-parameter tools.

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 verb ('Get') and resource ('Open Strategy Partners (OSP) On-Page SEO Optimization Guide'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this guide from sibling tools like 'get_meta_guide' or 'get_writing_guide', which might also be SEO-related guides.

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 guidance on when to use this tool versus alternatives like 'get_meta_guide' or 'get_writing_guide'. It doesn't mention prerequisites, context, or any exclusions, leaving the agent to infer usage based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/open-strategy-partners/osp_marketing_tools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server