Skip to main content
Glama

Update gate code / access notes

update_access_info
DestructiveIdempotent

Requires the connected Fold account. Saves how a driver gets in at one of the customer's saved addresses: gateCode (gate / building / lockbox code), howToGetIn (buzzer, doorman, side entrance), whereToLeaveBag. Drivers see these on every pickup and delivery there. Omit addressId for the default address. Pass an empty string to clear a field.

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

Input Schema

NameRequiredDescriptionDefault
gateCodeNoMax 40 chars.
addressIdNo
howToGetInNoMax 200 chars.
whereToLeaveBagNoMax 500 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds real context above that by disclosing blast radius ("Drivers see these on every pickup and delivery there") and the auth prerequisite, plus the empty-string-clears destructive convention. It leaves one meaningful gap: whether omitted fields are preserved or wiped on a partial update, which matters for a destructive write with zero required parameters.

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, front-loaded with the auth precondition and then the purpose, with each sentence carrying a distinct fact (effect, visibility, default address, clearing). Nothing is repeated from the schema or title.

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?

For a 4-parameter mutation with no output schema, the description covers auth, scope, the default-address shortcut, clearing semantics, and downstream visibility. The remaining omission is update semantics for fields you don't pass (merge vs. replace), which an agent would still have to guess.

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 75%, and the description compensates for the one undocumented parameter by explaining addressId's default-address behavior. It also adds driver-facing meaning to the fields beyond the schema's bare max-length notes. Length limits themselves are left to the schema, which is appropriate.

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 concrete verb and resource ("Saves how a driver gets in at one of the customer's saved addresses") and enumerates the three fields affected, so the effect is unambiguous. It is clearly distinguishable from the nearby update_* siblings (care preferences, notification preferences, recurring pickup) which handle unrelated settings.

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 a prerequisite ("Requires the connected Fold account") and two concrete calling rules: omit addressId to target the default address, and pass an empty string to clear a field. It does not name an alternative tool or state when *not* to use it, so it stops short of the 5 bar.

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