Skip to main content
Glama
Sign In
oda-mcp

oda-mcp

by amnotyoung
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

IATI BYOK 상태

iati_status
Read-onlyIdempotent

Verifies that a local IATI API key is configured for ODA data access. Does not read or expose the key value.

Instructions

로컬 IATI API 키가 설정됐는지만 확인합니다. 키 값은 읽어오거나 반환하지 않습니다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds transparency by stating it only checks existence and does not read or return the key value, which is behavioral context beyond annotations.

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?

The description is a single, efficient sentence with zero waste. It conveys the essential information without extraneous detail.

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 tool with no parameters and no output schema, the description fully specifies its function (checking key existence) and its limitation (not reading the key). No further detail is needed.

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?

No parameters exist, so schema coverage is 100%. The description adds no parameter information, which is acceptable as there are none. Baseline score of 4 applies for no params.

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?

The description clearly states it checks if the local IATI API key is set, with a specific verb 'checks' and resource 'local IATI API key'. It distinguishes from siblings by specifying it does not read or return the key value, which is unique among the sibling tools like iati_test_connection or country_list.

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 implies usage as a simple status check but does not explicitly guide when to use this tool vs alternatives like iati_test_connection. No exclusions or context about when not to use it, relying on the tool's narrow scope.

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