Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Baixar modelo de importação

get_import_template
Read-onlyIdempotent

Downloads the spreadsheet template accepted for import and saves it to the host export directory, returning the file path.

Instructions

Baixa o modelo de planilha aceito pela importação e grava no diretório de exportação do host. Retorna o caminho do arquivo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_import_template"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations by disclosing that a file is written to the host export directory and that the return value is a file path — neither is derivable from the empty schema. However, writing a file is in mild tension with readOnlyHint=true, and the description does not say whether an existing file is overwritten, what the filename is, or what happens if the export directory is unavailable.

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?

Two short sentences, front-loaded with the action and ending with the return value; nothing is redundant. There is little structure to evaluate given the brevity, but no wasted wording.

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 zero-parameter, non-destructive download tool with no output schema, the definition covers what it does, where the artifact lands, and what is returned. Only minor operational details (filename, overwrite semantics, failure modes) are missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the description misdescribes inputs.

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 states a specific verb+resource: it downloads the spreadsheet template accepted by the import process and saves it to the host's export directory, then returns the file path. This is concrete and distinguishable from the import-execution siblings, though it never names those siblings to draw the contrast 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 by the phrase 'modelo de planilha aceito pela importação' — an agent can infer it should be fetched before calling import_transactions or preview_transaction_import. There is no explicit when-to-use/when-not guidance or stated prerequisite (e.g. whether the template depends on settings or account type).

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