Skip to main content
Glama
Sign In
clearskies MCP Server

clearskies MCP Server

by clearskies-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_context_info

Retrieve detailed documentation for any specified clearskies context type. Use this to understand context options like Cli, WsgiRef, and Wsgi when generating code or scaffolding projects.

Instructions

Get detailed documentation for a specific clearskies context type.

Args:
    context_type: The name of the context type (e.g. "Cli", "WsgiRef", "Wsgi").

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context_type": "<context_type>"
    },
    "name": "get_context_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
context_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral details beyond the basic action of retrieving documentation. It does not mention error handling, required permissions, or side effects, leaving the agent without information on failure modes.

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 two sentences, front-loading the purpose and then detailing the parameter. No unnecessary information.

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?

This is a simple one-parameter tool with an output schema, so the description covers the essential purpose and parameter. However, it does not direct the agent to list_available_contexts for valid values, which would improve completeness.

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?

The input schema has no description for context_type (0% coverage). The description compensates by explaining the attribute and providing examples ('Cli', 'WsgiRef', 'Wsgi'), which adds meaningful context on what value to supply.

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 'Get detailed documentation for a specific clearskies context type', which uses a specific verb and resource. It distinguishes itself from sibling tools like list_available_contexts by focusing on a specific context type.

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 via the word 'specific', contrasting with list_available_contexts, but it does not explicitly mention when to use this tool over alternatives. No exclusions or alternative tool references are given.

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

Deploy Server

Other Tools