Skip to main content
Glama
Sign In
Keil5 MCP Server

Keil5 MCP Server

by ZMC1011
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

keil_version

Retrieve the Keil5 MCP server version and available tool count to confirm the integration is properly set up for STM32 project builds.

Instructions

Return the keil5-mcp server version and available tool count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keil_version"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the burden of explaining behavior. It explicitly says the tool only returns values, implying a read-only, non-destructive operation. Given the tool has zero parameters and no side effects, the description is sufficiently transparent for what the tool actually does.

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, compact sentence that immediately states what the tool returns. There is no filler, and the most important information is front-loaded. It earns its place without any wasted words.

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?

For a zero-parameter version query with no output schema, the description is complete: it tells the agent exactly what the tool returns. There are no prerequisites, inputs, or complex behaviors to document. Nothing meaningful is missing.

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 tool takes zero parameters, so there are no parameter semantics to explain. The input schema is empty and the description correctly does not attempt to describe nonexistent parameters. Baseline 4 applies here because there is nothing for the description to add.

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: returning the keil5-mcp server version and available tool count. It uses a specific verb and resource, so it is not tautological and is easy to understand. However, it does not explicitly contrast itself with sibling tools, though no sibling tool appears to overlap with this version-info purpose.

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?

No explicit guidance is provided for when to use this tool versus alternatives. The intended use is implied by the description—checking the server version and available tool count—but there is no stated context or exclusions. This is adequate for a trivial info-retrieval tool, but not exemplary.

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