Skip to main content
Glama

get_exchange_info

Read-onlyIdempotent

Retrieve general statistics for Kwork exchange, including project counts, categories, and limits. Use this tool to get an overview before managing projects.

Instructions

Общая статистика биржи Kwork: количество проектов, категории, лимиты.

Когда использовать: для получения общей информации о бирже перед работой с проектами. Возвращает: статистику биржи в виде ключ-значение. Связанные: list_projects — список проектов, list_categories — дерево категорий.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds that the output is key-value statistics, which is useful 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?

Three sentences: purpose, usage, related tools. No wasted words, front-loaded with key information.

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?

Despite no parameters, the description covers purpose, usage context, output format, and sibling relationships. An output schema exists, so return values are handled by that.

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% and the description naturally cannot add parameter info. The baseline of 4 applies as it doesn't need to compensate.

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 the tool returns general exchange statistics (number of projects, categories, limits) with a specific verb (get) and resource (exchange info). It distinguishes from siblings like list_projects and list_categories by focusing on overall stats.

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

Usage Guidelines5/5

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

Explicitly states when to use ('before working with projects') and lists related tools (list_projects, list_categories) as alternatives, providing clear guidance.

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/simonether/kwork-mcp'

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