Skip to main content
Glama
clearskies-py

clearskies MCP Server

generate_endpoint_group

Generate clearskies EndpointGroup configurations for your API by specifying URL prefix, endpoint list, and authentication.

Instructions

Generate a clearskies EndpointGroup configuration.

Args:
    url: The URL prefix for all endpoints in the group.
    endpoints: List of endpoint configurations. Each dict has:
        - type (str): Endpoint type (e.g. "RestfulApi", "Callable", "List")
        - model_name (str): Model class name (for model-based endpoints)
        - url (str): URL path for this endpoint
        - readable_column_names (list[str], optional): Readable columns
        - writeable_column_names (list[str], optional): Writeable columns
        - sortable_column_names (list[str], optional): Sortable columns
        - searchable_column_names (list[str], optional): Searchable columns
        - default_sort_column_name (str, optional): Default sort column
        - request_methods (list[str], optional): Allowed HTTP methods (for Callable)
        - extra_options (dict, optional): Additional endpoint options
    authentication: Authentication configuration for all endpoints in the group
        (e.g. 'clearskies.authentication.SecretBearer(environment_key="MY_SECRET")').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
endpointsNo
authenticationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It documents the input parameters in detail but does not mention side effects, whether it modifies the filesystem, requirements, or error behavior. It lacks transparency about what happens beyond returning a configuration object.

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 well-structured docstring with a clear first sentence followed by an Args block. Every bullet point adds necessary information about the endpoint configuration structure. It is lengthy but justifiable given the complexity of the `endpoints` parameter.

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

Completeness4/5

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

The description covers all three parameters and their semantics in depth, and an output schema exists for return values. However, it does not mention that `url` and `authentication` have empty-string defaults or that `endpoints` is optional (schema shows default null). This small gap prevents a perfect score.

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 input schema provides only types and titles (0% coverage), so the description must compensate. It does so thoroughly: for `endpoints` it enumerates all sub-fields with types and optionality, and for `authentication` it gives a concrete example. This adds substantial meaning beyond the schema.

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 begins with a specific verb and resource: 'Generate a clearskies EndpointGroup configuration.' This clearly distinguishes it from sibling tools like generate_endpoint (single endpoint) and scaffold_restful_api, which have broader 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 creating a group of endpoints with a shared URL prefix and authentication, but it does not explicitly state when to use this tool versus generate_endpoint or other alternatives. No exclusions or conditions are mentioned, so the guidance is implied rather than explicit.

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