Skip to main content
Glama

taxsort-mcp

by io.github.lonniev
OverviewDiscussionsAdmin

taxsort_report_issue

File a field report about this service as a GitHub issue on the operator's repo.

Found a tool's metadata or response wrong or confusing? Report it where the tool lives. The author of record is your npub — no npub / no proof, no issue — and it is stamped into the issue so the report is attributed to you, not the operator. Costs a small fee (a free write to an issue tracker would be abused). The report is PUBLIC and goes to the maintainers' normal triage; nothing is verified here.

Returns the filed issue's repo, number, and url. If this operator has not enabled field reports, returns an "issue reporting not configured" situation and you are not charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesThe details — which tool, what was wrong, what you expected.
npubYesYour Nostr public key (npub1...); the report's author of record.
titleYesOne-line summary of the problem.
tool_nameNoOptional: the specific tool the report is about (e.g. "schwab_get_option_chain").
dpop_tokenYesRaw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL; content:"", created_at within 60s of now, and a random `nonce` tag recommended. Or a cached dpop_token phrase.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"The details — which tool, what was wrong, what you expected."
    • addedInput schema / properties / dpop_token / description
      Added value: +"Raw JSON of a kind-27235 Nostr event signed by npub —\nnot base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its\n`u` tag must hold THIS tool's exact name (from tools/list), not\nthe endpoint URL; content:\"\", created_at within 60s of now, and a\nrandom `nonce` tag recommended. Or a cached dpop_token phrase."
    • addedInput schema / properties / npub / description
      Added value: +"Your Nostr public key (npub1...); the report's author of record."
    • addedInput schema / properties / title / description
      Added value: +"One-line summary of the problem."
    • addedInput schema / properties / tool_name / description
      Added value: +"Optional: the specific tool the report is about\n(e.g. \"schwab_get_option_chain\")."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the report costs a small fee, is public, is stamped with the caller's npub, goes to normal maintainer triage, is not verified, and charges nothing when field reports are not configured. This is far beyond a minimal mutation warning.

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 front-loaded with the core action and use case, then adds consequential facts in compact, scannable sentences. Each sentence contributes a distinct piece of information: purpose, trigger, attribution requirement, cost, publicity, success return, and failure mode.

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?

For a paid, public, attribution-sensitive tool with no annotations, the description is remarkably complete: it covers prerequisites, cost, privacy/publicity, verification behavior, the not-configured error case, and the return value. Parameter details and output structure are already supplied by the schema and output schema.

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 covers 100% of the parameters with detailed descriptions, so the description does not need to repeat parameter formats. It adds useful high-level context about the npub being the author of record and the fee, but no parameter-level semantic detail beyond the schema.

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 states a specific verb and resource: file a field report as a GitHub issue about this service on the operator's repo. It also frames the exact trigger ('Found a tool's metadata or response wrong or confusing?'), which separates it from general-purpose sibling tools like taxsort_create_feedback_issue.

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 clearly identifies when to use the tool ('Report it where the tool lives') and gives prerequisite conditions: the npub must be provided or there is no issue, and a fee applies. It does not explicitly name alternatives or state when not to use the tool, so it stops short of a 5.

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

All taxsort-mcp 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