Skip to main content
Glama
Sign In
spines-underground

spines-underground

by lisamaraventano-spine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-free-content

Retrieve free content from Spine's Underground — including agent tools, Overflow pieces, and Memory Palace pieces. Content is delivered inline by specifying a product ID.

Instructions

Get free content or tool info from Spine's Underground. 13 free products: 3 agent tools, 2 Overflow pieces, 8 Memory Palace pieces. Content delivered inline.

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": {
      "product_id": "<product_id>"
    },
    "name": "get-free-content"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct ID to retrieve (e.g. memory_threads, logic_bombs, pet_rock_lobster)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/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 mentions 'Content delivered inline' but does not disclose behavioral traits such as error handling for invalid product IDs, authentication requirements, rate limits, or side effects. Minimal disclosure beyond purpose.

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 concise (two sentences) with front-loaded purpose. Every sentence adds value: the first states the action and source, the second provides useful specifics about product counts. No wasted words.

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

Completeness4/5

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

For a simple one-parameter tool with no output schema and no annotations, the description is fairly complete. It covers what the tool does, the type of content, and delivery mechanism. Minor gaps include lack of error handling or edge case description, but these are acceptable given the tool's simplicity.

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?

Input schema has 100% description coverage for the single parameter 'product_id', including example values. The description adds no new semantic meaning beyond the schema; it only mentions the count of free products. Baseline 3 is appropriate since schema already documents the parameter well.

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 clearly states the verb 'get', the resource 'free content or tool info from Spine's Underground', and enumerates the 13 free products with categories. It distinguishes from sibling tools like browse, buy, search, and verify-receipt by focusing on free content retrieval.

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?

The description implies usage for accessing specific free products by ID, but does not explicitly state when to use this tool over siblings like browse-spines-underground or search-spines-underground. No exclusions or alternatives are mentioned.

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

Deploy Server

Other Tools