Skip to main content
Glama
Sign In

Serpier

by com.serpier
OverviewDiscussionsAdmin

serpier-guide

Read-only

Serpier's guides for AI agents: what Serpier's objects are, which ID each tool takes and where to get it, and the steps and rules of workflows such as buying links. Read serpier-basics before your first write, buying-links before you add to the cart or place an order, filling-order-details after an order is placed, ai-visibility-analysis before you analyse AI Visibility results, and suggestions when the user asks what to do next. Call with no arguments to list the guides, with skill to read one, and with skill and file to read one of its reference files. Read-only.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "serpier-guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoA file listed by the guide, e.g. 'references/ids.md'. Needs `skill`. Defaults to SKILL.md.
skillNoThe guide to read, e.g. 'serpier-basics'.
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds call-mode behavior: no skill lists guides, skill reads one guide, and skill+file reads a reference file. However, it does not reconcile the advertised no-argument mode with the required context and llm_model fields.

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

Conciseness4/5

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

The description is front-loaded with purpose, then routing rules, then invocation modes. It is dense but well ordered, with only minor redundancy such as the final 'Read-only' repeating the annotations.

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?

For a guide-retrieval tool with four parameters, no output schema, and rich schema descriptions, the description covers purpose, when to read each guide, and list/read modes. Its main gap is not reconciling the required context and llm_model analytics fields with the advertised no-argument list mode, leaving an agent to rely on schema validation for correct invocation.

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?

Schema coverage is 100%, so the context, llm_model, skill, and file schema descriptions already carry most parameter meaning; the baseline is 3. The description usefully maps skill values to workflow timing and explains reference files, but the phrase 'call with no arguments' conflicts with the two required analytics parameters and never mentions them, preventing a higher score.

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?

The description opens by stating these are Serpier's guides for AI agents and lists the concrete content: object definitions, which IDs tools take, where to get them, and workflow steps and rules. It clearly distinguishes this as documentation retrieval rather than an operational sibling like add-to-cart or get-order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-read rules for each named skill: serpier-basics before first write, buying-links before cart or order, filling-order-details after an order, ai-visibility-analysis before AI Visibility analysis, and suggestions when the user asks what to do next. It also explains list vs. skill vs. skill+file invocation modes.

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

All Serpier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources