Skip to main content
Glama

Read a Shipfound routine

routine
Read-only

The written procedure for a piece of work (grow, audit, status, seo, fix, write, list, launch, outbound, reach, boost, aso and the rest), the same text the plugin reads, with its pointers to other routines as routine calls; references/<name> for a reference, skill for the whole skill. Without a name, the list. Follow it as written; without the founder's code, read "open a PR" as giving the change to paste. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: the returned text is identical to what the plugin reads, cross-references appear as `routine` calls, and 'Free' signals no cost. The interpretation rule about 'open a PR' without the founder's code is a behavioral disclosure the annotations cannot carry.

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

Conciseness3/5

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

The content is front-loaded and dense, but it is delivered as one run-on sentence with a long parenthetical routine list that could be trimmed. Every clause is informative, yet the structure makes it harder to scan than it needs to be.

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 one-optional-parameter read tool with no output schema, the definition covers what is returned (procedure text with `routine` pointers), the no-name list mode, special name forms, and cost. Little an agent needs in order to call it correctly is missing.

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?

Schema coverage is 0%, so the description must carry the single optional `name` parameter, and it does: a name selects one routine, omitting it yields the list, and `references/<name>` and `skill` are documented special values. Only the 60-character constraint and exact name-matching rules are left to the schema.

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 states the resource precisely: 'the written procedure for a piece of work', 'the same text the plugin reads', and enumerates the routine families (grow, audit, status, seo, fix...) plus the special `references/<name>` and `skill` targets. That is enough to distinguish it from a data-reading sibling, though it never names a specific alternative tool.

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?

It gives a mode rule ('Without a name, the list') and an operating instruction ('Follow it as written'), which is genuine usage context. It stops short of saying when to reach for this versus another read tool or when not to call it, so the guidance is implied rather than explicit.

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