Skip to main content
Glama

Make a new access code

appSharingNewCode
Destructive

Make a new access code for one of your apps. The old code stops working. Requires confirmed: true, representing the human’s agreement.

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": {
      "projectId": "<projectId>",
      "confirmed": "<confirmed>"
    },
    "name": "appSharingNewCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes beyond them by specifying exactly what is destroyed: 'The old code stops working.' It also explains the confirmation contract as 'the human's agreement,' which tells the agent this must be a user-initiated action rather than an autonomous retry.

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?

Three short sentences, front-loaded with the action, then the destructive consequence, then the precondition. Every sentence adds information and none restates the title verbatim.

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, return values need not be described. The description covers the key behavioral risk (old code invalidation) and the consent precondition, which are the two things an agent must know before invoking. It could say slightly more about the blast radius, e.g. whether existing users are signed out, but it is largely complete for a two-parameter 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 0%, so the description carries the burden. It explains confirmed well, adding the intent behind the const:true constraint, but projectId is only obliquely covered by 'one of your apps' — the agent gets no guidance on where the UUID comes from, though the uuid format is in the schema.

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 description names a specific verb and resource: 'Make a new access code for one of your apps,' which is clearly distinct from sibling operations like appSharingAddPeople or appSharingSetMode. It does not explicitly name an alternative tool, so it stops short of full sibling routing guidance, but the action is unambiguous.

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 phrase 'for one of your apps' and by the confirmed:true requirement, which signals this is a deliberate, consent-gated action. However, there is no explicit statement of when to rotate a code versus when to change sharing mode or membership, and no stated exclusions.

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