Skip to main content
Glama

Remove a building permit from a list

remove_permit_from_list
DestructiveIdempotent

Removes one building permit from a list. Removing a permit that is not on the list changes nothing. Does not use credits.

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": {
      "listId": "<listId>",
      "permitId": "<permitId>"
    },
    "name": "remove_permit_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list's public id ("lst_…"), from list_user_lists.
permitIdYesA permit id (permitId on a permit record).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds two genuinely useful facts beyond that: removing a non-member permit is a silent no-op, and the call consumes no credits. It stops short of clarifying that only the list membership is affected and the underlying permit record survives.

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 operation and followed by the two edge-case facts an agent actually needs. Nothing is padded or repeated for its own sake.

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 two-parameter tool with a fully described schema and annotations covering destructiveness and idempotency, the description supplies the remaining operational facts (no-op behavior, no credit cost). The only gap is not stating explicitly that the permit record itself is untouched.

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%, with listId documented as a "lst_…" public id sourced from list_user_lists and permitId as a positive integer permit record id. The description adds nothing further about either parameter, so the baseline 3 applies.

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 states a specific verb and resource: "Removes one building permit from a list," which is unambiguous about the operation and its target. It does not, however, differentiate itself from the sibling remove_from_list, so an agent must infer the boundary from the names alone.

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 only implied by the operation itself — an agent can infer it is used when a permit should be detached from a specific list. There is no explicit when-to-use statement, no mention of when to prefer remove_from_list instead, and no stated prerequisites such as needing the list id from list_user_lists (that hint lives only in the schema).

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