Skip to main content
Glama
Sign In
Budgetsco MCP Server

Budgetsco MCP Server

by drishit96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Currency

getCurrency
Read-onlyIdempotent

Retrieve the current currency preference for your Budgetsco account to ensure accurate financial tracking and multi-currency transactions.

Instructions

Get the current currency preference

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": "getCurrency"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.8
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only 'current', which is a minor clarification and does not provide additional behavioral context like return format or caching. Given the annotations, this is adequate but not enriching.

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?

A single sentence that states exactly what the tool does with no wasted words. It is front-loaded and perfectly scoped for its simplicity.

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 parameterless, read-only getter with annotations covering safety, the description is complete. No output schema exists, but the description sufficiently communicates the purpose. An agent can call this correctly without further information.

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 has zero parameters, so the schema is trivially complete (100% coverage). The baseline for 0 params is 4, and the description does not need to add any parameter semantics. It correctly stays silent on parameters.

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 clear verb ('Get') and a specific resource ('current currency preference'). It unambiguously distinguishes from the sibling setCurrency, which is the corresponding write operation. An agent can immediately tell this is a read-only retrieval of the user's currency setting.

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 purpose implies usage: read the current currency preference. The sibling setCurrency provides the contrast for write operations, though the description does not explicitly state 'use this to read, setCurrency to write'. Still, the context is clear enough for an agent to select it appropriately.

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