Skip to main content
Glama

advice

by io.github.pipeworx-io

Get Advice

get_advice
Read-onlyIdempotent

Get a specific advice slip by its numeric ID (e.g., "42"). Returns the full advice text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe numeric ID of the advice slip to retrieve.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric ID of the advice slip
hintNoHow to get a valid id, when found is false
foundYesFalse when no slip has that id
adviceNoThe advice text (present when found)
reasonNoWhy nothing was returned, when found is false

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / advice / description
      Previous value: -"The advice text"New value: +"The advice text (present when found)"
    • addedOutput schema / properties / found
      Added value: +{
+  "description": "False when no slip has that id",
+  "type": "boolean"
+}
    • addedOutput schema / properties / hint
      Added value: +{
+  "description": "How to get a valid id, when found is false",
+  "type": "string"
+}
    • addedOutput schema / properties / reason
      Added value: +{
+  "description": "Why nothing was returned, when found is false",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "advice"
-]New value: +[
+  "found",
+  "id"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "advice": {
+      "description": "The advice text",
+      "type": "string"
+    },
+    "id": {
+      "description": "Numeric ID of the advice slip",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "advice"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 42
+  },
+  {
+    "id": 117
+  }
+]
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds only that it returns the 'full advice text,' which is minimal but not conflicting.

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 sentence with no extraneous content. It includes a helpful example ID without wasting 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 read tool with comprehensive annotations and an output schema, the description covers the essential purpose and usage. It doesn't mention not-found behavior, but the output schema and structured context likely fill that gap.

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?

The input schema already provides a complete description of the 'id' parameter with 100% coverage. The description repeats the ID requirement and gives an example, adding no substantive new semantics.

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 uses the verb 'Get' with a specific resource ('advice slip') and identifies the retrieval method ('by its numeric ID'). This clearly distinguishes it from sibling tools like random_advice and search_advice.

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

Usage Guidelines4/5

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

The description implies that the tool is appropriate when a specific numeric ID is known, which is clear context. However, it doesn't explicitly mention alternatives or when not to use it, so it falls short of full guidance.

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

All advice toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

The ask_pipeworx family is a major confusion source: ask_pipeworx_beta explicitly states it 'currently matches ask_pipeworx exactly', and ask_pipeworx_grounded/deep_research heavily overlap with the base router. polymarket_edges vs polymarket_arbitrage and discover_tools vs suggest_questions also have fuzzy boundaries, though long descriptions partially mitigate the overlap.

Naming Consistency4/5

All tool names are lowercase snake_case, and most follow a verb_noun pattern (validate_claim, resolve_entity, compare_entities, generate_llms_txt). A few bare verbs (remember, recall, forget) and noun-style names (entity_profile, polymarket_arbitrage, pipeworx_trending) deviate slightly, but the overall style is predictable and readable.

Tool Count2/5

34 tools is heavy and spans several unrelated domains: Pipeworx data research, prediction markets, subscriptions, memory, AI visibility, advice slips, npm dependency checks, and llms.txt generation. The count is inflated by near-duplicate research routers and disconnected outliers like generate_llms_txt and scan_dependency, making the set feel like a kitchen sink rather than a focused server.

Completeness3/5

The Pipeworx research and prediction-market surfaces are quite complete (ask, grounded, deep research, entity profile, compare, resolve, validate, subscriptions with full lifecycle, memory with save/recall/delete). However, the server is named 'advice' yet the advice domain only has three thin tools (get/search/random) with no other operations, and the mixed domains leave obvious dead ends for any single stated purpose.

Resources