Skip to main content
Glama
clearskies-py

clearskies MCP Server

generate_endpoint

Generate a clearskies endpoint configuration by specifying endpoint type and model name, with options for URL, columns, authentication, and extra settings.

Instructions

Generate a clearskies endpoint configuration.

Args:
    endpoint_type: Type of endpoint (e.g. "RestfulApi", "List", "Create", "Get", "Update", "Delete", "Callable").
    model_name: The model class name to use with this endpoint.
    url: The URL path for the endpoint (optional).
    readable_column_names: List of column names that are returned in the response.
    writeable_column_names: List of column names the client can set.
    sortable_column_names: List of column names the client can sort by.
    searchable_column_names: List of column names the client can search by.
    default_sort_column_name: The default column to sort by.
    authentication: Authentication configuration (e.g. 'clearskies.authentication.SecretBearer(environment_key="MY_SECRET")').
    extra_options: Additional keyword arguments for the endpoint constructor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
model_nameYes
endpoint_typeYes
extra_optionsNo
authenticationNo
readable_column_namesNo
sortable_column_namesNo
writeable_column_namesNo
searchable_column_namesNo
default_sort_column_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'generate' without explaining whether the tool returns a configuration object, writes to a file, mutates state, or requires authentication. No side effects or prerequisites are mentioned.

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 opens with a one-sentence purpose statement followed by a terse, well-organized Args list. Every line adds value, with no fluff or redundancy. The structure is front-loaded and efficient for an agent to parse.

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

Completeness3/5

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

The parameter list is comprehensive, and an output schema exists so return values are covered. However, the overall behavior of 'generate' remains ambiguous, and there is no discussion of prerequisites, workflow context, or how the generated configuration is consumed. The description is adequate but has clear gaps.

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?

Schema description coverage is 0%, so the description is the only source of parameter meaning. It explains all 10 parameters with practical examples (e.g., endpoint_type examples, authentication format) and clarifies the role of each column list. This fully compensates for the lack of schema descriptions.

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 'Generate a clearskies endpoint configuration' with a specific verb and resource. It distinguishes from sibling tools like generate_model, generate_context, and generate_endpoint_group by focusing on endpoint configuration.

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 such as generate_endpoint_group or scaffold_restful_api. The description only lists parameters and gives no contextual or exclusionary instructions.

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