Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Sugerir categoria para item do inbox

suggest_inbox_item
Read-onlyIdempotent

Preview which category and person rules would assign to an inbox item before confirming changes, so you can verify outcomes without altering data.

Instructions

Mostra qual categoria e pessoa as regras aplicariam a um item da caixa de entrada, sem confirmar nada.

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": {
      "inboxItemId": "<inboxItemId>"
    },
    "name": "suggest_inbox_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
inboxItemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds the useful nuance that rule evaluation is hypothetical and nothing is committed, but says nothing about what happens when no rule matches or what the response contains.

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?

A single short sentence with the purpose front-loaded and the no-side-effect qualifier closing it; there is no filler, though it is terse enough to leave several points unstated.

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

Completeness3/5

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

For a one-parameter read-only tool this is roughly adequate, but with no output schema the description should clarify the returned shape (e.g., what is shown when no rule matches) and identify the sole parameter; neither is addressed.

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?

Schema description coverage is 0%, but there is only one parameter (inboxItemId, uuid) whose meaning is largely carried by its name and format. The description adds no detail about the parameter, so the baseline of 3 for a near-self-explanatory single param is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Mostra") plus a concretely scoped result: the category and person the rules would assign to an inbox item. The phrase "sem confirmar nada" implicitly separates it from the confirmation sibling, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a preview/dry-run check to run before confirming, but the description never states when to prefer it over confirm_inbox_item or what precondition (e.g., item still pending) matters.

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