Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

get_sketch

Read-onlyIdempotent

List files in a saved sketch or read a sketch-relative file's UTF-8 text and SHA-256 to inspect its contents.

Instructions

List files in a saved sketch. Specify a sketch-relative file to read its UTF-8 text and SHA-256.

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": {
      "sketch": "<sketch>"
    },
    "name": "get_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
sketchYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
statusYes
warningsNo
request_idNo
next_actionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them: the tool has two distinct operating modes depending on whether 'file' is set, and file reads return UTF-8 text plus a SHA-256 digest. It does not say what happens for a nonexistent or binary file, which keeps it below a 5.

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 sentences, zero filler, and the primary list behavior is front-loaded ahead of the conditional read behavior. Every clause conveys information not present in the name or schema.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile, so the remaining burden is small and mostly met. Error behavior (missing sketch, unreadable file) and the preconditions for a sketch existing are the only notable gaps for a two-parameter read tool.

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?

Schema coverage is 0%, so the description must carry parameter meaning, and it does: 'sketch' is a saved sketch and 'file' is a sketch-relative path, with the optional nature of 'file' explained via the list-vs-read distinction. What is missing is format guidance (path separators, whether directories/subpaths are allowed) for the 512-char 'file' string.

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?

Names a specific verb and resource ('List files in a saved sketch') and adds a second mode ('read its UTF-8 text and SHA-256' when a file is specified). An agent can tell this apart from list_sketches or write_sketch_file by the 'saved sketch' scoping, though it never explicitly contrasts with those siblings.

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?

Usage is implied by the two-mode wording: omit 'file' to list, supply 'file' to read contents. There is no explicit when-not guidance, no mention of prerequisites (does the sketch need to be compiled or created first?), and no named alternative such as write_sketch_file for the mutation case.

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