Skip to main content
Glama
Sign In
clearskies MCP Server

clearskies MCP Server

by clearskies-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_query_result_info

Get detailed documentation for a specific clearskies query result type, explaining its structure and how to use it in your applications.

Instructions

Get detailed documentation for a specific clearskies query result type.

Args:
    result_type: The query result type name.

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": {
      "result_type": "<result_type>"
    },
    "name": "get_query_result_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
result_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

C2.8/5.0
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 for behavioral disclosure. It does not explicitly state that the operation is read-only, nor does it mention errors, permissions, or side effects, leaving the agent with minimal guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and includes a structured Args block. While the Args block is somewhat redundant with the schema, it does not waste words and maintains clarity.

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?

For a simple one-parameter info tool with an output schema, the description is minimally adequate. However, it lacks context on how this tool relates to sibling tools or where to find valid result type names, and the absence of annotations leaves behavioral aspects uncovered.

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

Parameters2/5

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

The description adds little meaning beyond the input schema, simply restating the parameter as 'The query result type name.' It offers no examples, valid values, or link to listing tools, which is insufficient given 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: retrieving detailed documentation for a specific clearskies query result type. It uses a specific verb ('Get') and resource, but does not differentiate it from sibling tools like get_query_info or list_available_query_results.

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. The description only includes a parameter listing, with no context about prerequisites, complementing tools, or exclusions.

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