Skip to main content
Glama
Sign In

Agent Tools

by dev.workers.jbarkules.agent-tools
OverviewDiscussionsAdmin

agent_context

International context bundle for scheduling, invoicing and coordination across borders. Combines timezone conversion, holiday calendar and currency exchange in one call. Returns DST-correct local time with offset, upcoming public holidays and exchange rate. Sources: IANA TZDB, Nager.Date API, European Central Bank. Price $0.003 USDC per call via x402. Example output: {"country":"US","timezone":"America/New_York","local_time":{"datetime":"2026-03-15T08:00:00","utc_offset":"-04:00"},"holidays":{"year":2026,"count":11,"upcoming":[{"date":"2026-05-25","name":"Memorial Day"},{"date":"2026-07-04","name":"Independence Day"}]},"exchange_rate":{"from":"USD","to":"EUR","r

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": {
      "country": "<country>",
      "timezone": "<timezone>",
      "from_currency": "<from_currency>",
      "to_currency": "<to_currency>"
    },
    "name": "agent_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional year for holidays, default current year
countryYesISO 3166 alpha-2, e.g. US
timezoneYesIANA timezone, e.g. America/New_York
timestampNoOptional ISO datetime or 'now', default now
to_currencyYesTarget currency code, e.g. EUR
from_currencyYesSource currency code, e.g. USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does much of it: it discloses the underlying sources (IANA TZDB, Nager.Date, ECB), promises DST-correct offsets, states the per-call price of $0.003 USDC via x402, and sketches the returned structure. It stops short of failure modes, rate limits, or what happens when a country/currency pair is unsupported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the source and pricing sentences earn their place, but the trailing example output is truncated mid-string ('"r') and largely restates what the prose already covered, leaving the definition looking cut off rather than tight.

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 six-parameter, multi-domain tool with no output schema and no annotations, the description conveys return contents (local datetime plus offset, upcoming holidays, exchange rate) and the cost of invoking it, which is what an agent most needs. It is short only on error/edge-case behavior and on validation expectations for the required country and currency codes.

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 100%, so the baseline applies; all six parameters already document formats and defaults. The description adds the useful implication that the timestamp drives DST-correct local time output and that the year parameter scopes the holiday list, but nothing beyond what the schema already provides.

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 first two sentences name the composite resource precisely: timezone conversion, holiday calendar and currency exchange bundled into a single call, framed for cross-border scheduling and invoicing. It is clear what the tool does, but it never distinguishes itself from sibling single-purpose tools such as fx_convert, fx_rates or public_holidays.

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 'for scheduling, invoicing and coordination across borders', which suggests the cross-border composite scenario. There is no explicit when-to-use versus when-not guidance, no statement of prerequisites (e.g. that country and both currency codes are mandatory and must be valid codes), and no routing to the narrower sibling tools.

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

All Agent Tools 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