Skip to main content
Glama
clearskies-py

clearskies MCP Server

explain_concept

Provides detailed explanations of clearskies framework concepts, enabling developers to understand models, endpoints, and other key features.

Instructions

Explain a clearskies framework concept in detail.

Args:
    concept: The concept to explain. One of: model, endpoint, backend, column, context, di,
             authentication, autodoc, query, validator, schema, save_lifecycle, state_machine,
             declarative_programming, infrastructure_neutral, testing, authorization, error_handling,
             input_handling, endpoint_groups, routing, responses, migrations, advanced_columns,
             advanced_queries, configuration, logging, caching, async, state_machine_advanced,
             secrets_backend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conceptYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. 'Explain in detail' suggests a free-form informational response, but it does not explicitly state whether the operation is read-only, what output format to expect, or any other behavioral traits. However, the purpose is clear and non-destructive.

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, focused sentence followed by a clean list of valid concepts. It is front-loaded and wastes no words, making it easy to parse and understand.

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?

The tool is simple with one parameter, an output schema exists, and the description provides the complete set of valid inputs. There is no missing information about return values or side effects that is necessary for competent use.

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

Parameters5/5

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

The schema provides zero description coverage, but the tool description fully enumerates all valid values for the 'concept' parameter. This compensates entirely for the missing schema documentation and gives complete semantic meaning.

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 uses a specific verb ('Explain') and names the resource ('clearskies framework concept'), clearly distinguishing it from sibling tools that provide info about specific components or differences. The list of valid concepts further clarifies the exact scope.

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 for conceptual explanations, but it does not explicitly state when to choose this tool over alternatives like explain_module or get_* tools. No exclusions or alternative guidance is provided.

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/clearskies-py/mcp-server'

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