Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a help article

get_help
Read-only

Reads one Beeswax Shares help article in full by slug, so you can explain an app feature in its own terms before pointing the user to the page.

Instructions

Read one Beeswax Shares help article in full (Markdown), by slug from search_help. Use it to explain how a part of the app works in the app's own terms before pointing the user at the page.

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": {
      "slug": "<slug>"
    },
    "name": "get_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesArticle slug, e.g. "holdings" or "bank-feeds"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds that the return payload is the complete article in Markdown and that the slug must originate from search_help. It does not say what happens for an unknown or stale slug, which is the remaining gap for a fetch-by-identifier tool.

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?

One sentence plus one usage clause, front-loaded with the action and return format, with no redundant restatement of the title or schema.

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 single-parameter read tool with no output schema, the description supplies the return format and the upstream dependency, which is nearly everything needed. Only error behavior for a bad slug is unaddressed, a minor omission at this complexity.

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% and already documents the slug with examples, so the baseline is 3. The description earns one more by specifying provenance of the value ('slug from search_help'), which tells the agent not to invent slugs.

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?

States a specific verb and resource (read one help article in full, as Markdown) and pins the input to a slug obtained from search_help. That cleanly separates it from search_help (discovery) and find_page (page lookup) without opening any schema.

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?

Gives clear intended usage: explain how part of the app works in the app's own terms before pointing the user at the page. It implies a two-step flow with search_help but never states an explicit when-not-to-use case or contrast with find_page.

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