Skip to main content
Glama

Manawa Terminal

Report a bug

report_bug

Log a bug in the same inbox as the terminal bug button (5 per user per day).

Use only when the user asks, or when you have confirmed a real data/UI
error. Do not file speculative bugs. Pass ticker/section so admins get a
terminal URL; page_url is optional if it is already a terminal.manawa.app link.
Prefer block_id (registry.ui_blocks id) when the bug is tied to a page
element; include item_ids and developer_note when known.

Args:
    description: What is wrong (10–2000 characters)
    ticker: Optional stock symbol the bug is about
    section: Optional tab (overview, financials, thesis, valuation, …)
    page_url: Optional full terminal URL if already known
    block_id: Optional registry.ui_blocks id for the page element
    item_ids: Optional provenance / store item ids related to the bug
    developer_note: Optional note for developers (repro steps, flags, etc.)

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": {
      "description": "<description>"
    },
    "name": "report_bug"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerNo
sectionNo
block_idNo
item_idsNo
page_urlNo
descriptionYes
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.
developer_noteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / block_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Block Id"
      +}
    • addedInput schema / properties / developer_note
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Developer Note"
      +}
    • addedInput schema / properties / item_ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Item Ids"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare that this is a non-destructive write; the description adds the rate limit (5 per user per day), where the record surfaces (admin inbox), and the consequence of omitting ticker/section (no terminal URL for admins). It also clarifies that page_url is optional when the page is already a terminal.manawa.app link, which is side-effect-relevant context not present in annotations.

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 governing rules are front-loaded in three tight sentences, then an Args block adds the per-parameter detail. There is mild duplication between the prose (ticker/section, page_url, block_id, item_ids) and the Args list, but the Args entries carry extra specifics, so little is wasted.

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 an 8-parameter mutation tool this is complete: trigger conditions, rate limit, destination, parameter semantics, and prioritization (prefer block_id when tied to a page element) are all covered. An output schema exists, so return values need not be described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13%, and the description compensates: it documents 7 of 8 parameters with meaning the schema lacks — the 10–2000 character bound on description, section examples (overview, financials, thesis, valuation), what block_id refers to (registry.ui_blocks id), and item_ids as provenance/store ids. Only strategy_id is left to the schema, where it is already documented.

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 ("Log a bug") plus the destination behavior — it lands in the same inbox as the terminal bug button — which no sibling tool touches. An agent can distinguish it from every other write tool in the sibling list without opening the schema.

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?

Gives an explicit trigger ("Use only when the user asks, or when you have confirmed a real data/UI error") and an explicit exclusion ("Do not file speculative bugs"). That is a genuine when/when-not rule with a stated evidence bar, not an implied one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources