Skip to main content
Glama
Sign In
board-spec-mcp

board-spec-mcp

by roshs189
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_partition_conf_fields

Retrieves the partition_conf section of a board spec for a given machine, providing its partition table configuration.

Instructions

Return only the partition_conf section of a board's spec.

Use this from the qcom-partition-conf-new-board skill instead of parsing a Confluence page's Partition Table / contents.xml.in Metadata sections.

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": {
      "machine": "<machine>"
    },
    "name": "get_partition_conf_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
machineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Description indicates a read-only retrieval of a specific configuration section, but lacks details on permissions or error states; annotations missing so description carries burden, but is adequate for a simple query.

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?

Two concise sentences front-load the purpose and usage, with no extraneous 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?

Sufficient for a simple retrieval tool with one parameter; however, lacks output schema details and error behavior, but the core intent is well-covered.

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

Parameters1/5

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

Single parameter 'machine' has 0% schema description coverage, and the description does not mention or explain the parameter, failing to add any meaning beyond the name.

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?

Describes specific verb 'Return' and resource 'partition_conf section of a board's spec', clearly distinguishing from alternative methods like parsing Confluence pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('from the qcom-partition-conf-new-board skill') and what to avoid ('instead of parsing a Confluence page...'), providing clear context among sibling tools.

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