Skip to main content
Glama
Sign In

Foundaree

by io.github.shujahmhd
OverviewDiscussionsAdmin

Change a QR code

update_qr_code

Change one of the signed-in user's QR codes: point it to a new link, rename it, pause it or switch it back on. The printed QR stays exactly the same; the next scan opens the new link. A paused QR shows a "paused" page instead of the link until it is switched back on. Get the id from my_qr_codes. Read the change back to the user before calling this.

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": {
      "id": "<id>"
    },
    "name": "update_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe QR id (10 letters and numbers), from my_qr_codes or create_qr_code.
linkNoThe new link it should open.
nameNoA new name.
statusNo"paused" to stop it for now, "active" to switch it back on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by explaining that the printed QR is immutable and the next scan resolves to the new link, and that a paused code serves a 'paused' page until reactivated — key consequences for a mutation the agent might otherwise fear is destructive. It does not cover error behavior (invalid link, unknown id) or whether omitted fields are left untouched.

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 short sentences, each carrying distinct information: capabilities first, then the immutability consequence, then the paused-state behavior, then the id source and confirmation step. No repetition of the title 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 no output schema, the description still tells the agent what the observable outcome is (next scan opens the new link, paused page while paused) and that a user confirmation step precedes the call. Only the partial-update semantics and failure modes are left unstated for a 4-parameter mutation tool.

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 description coverage is 100%, so the baseline is 3. The description does add real meaning for 'status' by explaining the paused-page behavior, and points to my_qr_codes for the id, but it never states that parameters are optional/partial-update, which is the main semantic gap left to the schema.

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?

States a specific verb and resource ('Change one of the signed-in user's QR codes') and enumerates the exact operations: repoint the link, rename, pause, reactivate. The scope ('signed-in user's') plus the explicit capability list cleanly separates it from create_qr_code, delete_qr_code and my_qr_codes.

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

Usage Guidelines4/5

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

Gives concrete pre-call guidance: obtain the id from my_qr_codes, and read the intended change back to the user before calling. It does not explicitly name delete_qr_code or create_qr_code as the alternatives for removal/creation, but the 'change an existing code' framing makes the boundary clear.

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

All Foundaree toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources