Skip to main content
Glama

Create an upload link

create_upload_link

Give the user a short-lived link that opens BoardRepo's upload page for a KiCad project folder from their computer. Use when the user wants to store a board and you cannot read their files, or the project is not on GitHub. The link works only for the signed-in BoardRepo account that connected this assistant and expires after 15 minutes; it does not sign anyone in. Pass board (handle/slug of their own board) to upload a new version of it; omit to create a new board. Show the returned URL to the user; do not open it yourself. Only on the user's request.

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": "create_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNohandle/slug of one of the user's own boards to receive a new version. Omit to create a new board.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which only declare non-read-only, non-destructive, non-idempotent), the description discloses the 15-minute expiry, that the link is bound to the signed-in BoardRepo account that connected the assistant, and that it does not sign anyone in. These are exactly the operational traits an agent cannot infer from readOnlyHint/destructiveHint.

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?

Four sentences, each carrying a distinct load: purpose, trigger, security/expiry behavior, parameter effect, and output handling. The core capability and the critical expiry constraint are front-loaded with no filler.

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?

With one optional parameter, full schema coverage, and an output schema covering return values, the description fills every remaining gap: when to use it, who the link is valid for, how long it lives, and what the agent should do with the result.

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

Parameters3/5

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

Schema coverage is 100% and the schema's own 'board' description already states 'omit to create a new board', so the description's restatement ('Pass board ... omit to create a new board') adds little new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence names a specific verb and artifact ('give the user a short-lived link that opens BoardRepo's upload page') and scopes it to a KiCad project folder from the user's computer. The phrase 'or the project is not on GitHub' implicitly separates it from GitHub-import and push-style siblings, though no sibling is named outright.

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?

It gives explicit trigger conditions ('when the user wants to store a board and you cannot read their files, or the project is not on GitHub') and explicit exclusions, plus the constraint 'Only on the user's request' to prevent proactive creation. It also directs post-call handling: show the URL, do not open it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources