Skip to main content
Glama
Sign In

Mofi

by br.com.omofi
OverviewDiscussionsAdmin

Get classification rules

mofi_classifications_get
Read-onlyIdempotent

Lists the canonical categories and supported exact-match provider rules. Rule coverage is partial; unknown or conflicting labels are not guessed. Personal overrides from mofi_classifications_save are applied to transaction, spending, and recurring results; source labels remain unchanged.

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": {
      "mode": "<mode>"
    },
    "name": "mofi_classifications_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNo
modeNo
errorNoTyped error (code, message, retryable, details); set when isError is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description still adds real substance: partial rule coverage, a deliberate no-guessing policy on unknown or conflicting labels, and the fact that personal overrides are reflected in transaction, spending and recurring results while source labels stay unchanged. That override-versus-source distinction is behavior an agent could not derive from the annotations or schema.

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?

Three tight sentences, each carrying distinct information: scope, coverage limits, and override propagation semantics. Front-loaded with the resource definition and free of filler.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description covers the substantive gaps an agent would care about (partial coverage, no guessing, override behavior). Only the unexplained 'mode' parameter keeps it short of full completeness.

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% and the description says nothing about the single required 'mode' parameter. However, the schema pins it to a const value ('findAll'), so it is fully self-constraining and needs little prose support. Adequate but adds no meaning beyond the schema.

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?

States a specific verb and resource: it lists canonical categories plus supported exact-match provider rules. It also implicitly separates itself from mofi_classifications_save by noting that save-produced overrides are applied downstream rather than stored here. The only unclear element is the odd 'mode: findAll' input, which the description never explains.

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?

The description establishes context (rule coverage is partial, unknown or conflicting labels are not guessed, overrides affect transaction/spending/recurring results) but never explicitly states when to call this versus the sibling get tools or save. Usage is inferable rather than directed.

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

All Mofi 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