Skip to main content
Glama
gitbosung

open-ALIO-mcp

by gitbosung

get_evaluation_indicator_detail

Retrieve detailed evaluation content, scores, and indicator definitions for Korean public institution performance indicators by specifying the indicator name.

Instructions

평가지표명으로 세부평가내용·배점·지표정의를 조회합니다.

예: '안전 및 재난관리', '총인건비관리', '윤리경영'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
yearNo
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It does not state it's a read-only operation, what happens on invalid input, or whether results are paginated. Only the basic query operation is hinted.

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 extremely concise—two sentences that immediately convey the tool's function with examples. No redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and low schema coverage, the description should provide more context such as return format, error handling, and the role of the year parameter. It is insufficient for an agent to reliably use this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description explains the query parameter (indicator name) with examples, but the year parameter is completely ignored, leaving its purpose and usage unclear.

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 clearly states it queries detailed evaluation content, scoring, and indicator definitions by indicator name. It gives concrete examples, making purpose evident. However, it does not explicitly differentiate from sibling tools like list_evaluation_indicators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitbosung/open-ALIO-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server