Skip to main content
Glama

Mastodon

by io.github.pipeworx-io

What Can I Ask Pipeworx?

suggest_questions
Read-onlyIdempotent

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate read-only, open-world, idempotent, non-destructive behavior. The description adds valuable context: returns category-bucketed example questions with tool arguments, drawn from a live catalog. No contradictions.

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?

Description is front-loaded with common queries, then structured with details. While lengthy, each sentence provides necessary context without redundancy. Could be slightly more concise but remains effective.

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

Completeness5/5

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

No output schema exists, so the description fully covers what is returned (category-bucketed example questions with exact tool and argument shape). Also explains the source (live catalog) and optional topic filtering. Complete for this tool.

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 100%, but the description adds meaning by specifying example topics (finance, pharma, etc.) and explaining that omitting topic yields a cross-category spread. This aids agent in parameter selection.

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 clearly states the tool's purpose as an onboarding entry point for new agents, providing example questions. It distinguishes itself by recommending use before exploring other tools and names sibling meta-tools like ask_pipeworx.

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?

Explicitly states when to use: when the agent doesn't know Pipeworx's capabilities or to learn meta-tools. Also explains optional topic parameter for focus, and lists sibling tools as alternatives for specific queries.

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

All Mastodon 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.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap between research-oriented tools like ask_pipeworx and deep_research, and between entity_profile and compare_entities. Descriptions help differentiate them, so overall an agent can tell them apart.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ask_pipeworx, list_subscriptions) and camelCase (bag_research, compare_entities). There is no uniform naming pattern, which can be confusing.

Tool Count2/5

With 35 tools, the set is too large for a server named 'Mastodon'. Only a few tools are actually Mastodon-related (e.g., get_account, get_timeline), while the majority are PipeWorx tools unrelated to the core purpose.

Completeness1/5

As a Mastodon server, the toolset is severely incomplete: it lacks basic social media operations like posting statuses, following/unfollowing, and engaging with content. The name misrepresents the actual capabilities.

Resources