Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
health_checkB

Check if the server is running and can access its resources

get_editing_codesB

Get the Open Strategy Partners (OSP) editing codes documentation and usage protocol for editing texts.

get_writing_guideB

Get the Open Strategy Partners (OSP) writing guide and usage protocol for editing texts.

get_meta_guideC

Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System (titles, meta-titles, slugs).

get_value_map_positioning_guideB

Get the Open Strategy Partners (OSP) Product Communications Value Map Generation System for Product Positioning (value cases, feature extraction, taglines).

get_on_page_seo_guideB

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific documentation or guides (editing codes, meta guide, SEO guide, value map, writing guide, health check). There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'get_' prefix for documentation retrieval tools and a clear descriptive noun (e.g., get_editing_codes, get_meta_guide). The health_check tool also fits a standard naming convention, maintaining uniformity throughout the set.

Tool Count4/5

With 6 tools, the count is reasonable and well-scoped for a marketing documentation server, covering key areas like editing, SEO, and positioning. It's slightly lean but appropriate, as each tool serves a distinct purpose without redundancy.

Completeness3/5

The tool set provides comprehensive retrieval for various marketing guides, but it lacks CRUD operations (e.g., create or update guides) and other lifecycle actions. This is a notable gap, as agents can only get information without modifying or interacting beyond basic health checks.

Maintenance

ActivityInactive
ResponsivenessUnresponsive