Skip to main content
Glama
Sign In

ApplyAll

by com.applyall
OverviewDiscussionsAdmin

Remove a blocklist entry

remove_blocklist_entry
Destructive

Remove an employer block by id from get_profile.

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": {
      "entryId": "<entryId>"
    },
    "name": "remove_blocklist_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdYesBlocklist row id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The description adds no behavioral details beyond the schema and annotations. Annotations already set destructiveHint=true, but the description does not elaborate on irreversibility, side effects, or required permissions. It offers no additional transparency beyond what is already structured.

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?

The description is a single, direct sentence with no superfluous words. The verb is front-loaded, and it gets straight to the point. Extremely efficient for a simple operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter, no output schema, and is destructive, the description is minimal but lacks key context. It does not mention the return value, side effects, or any caution about the permanent nature of removal. While annotations cover the destructive hint, the description could enhance completeness by stating consequences.

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 entryId documented as 'Blocklist row id.' The description does not add further meaning to the parameter. Since the schema fully covers the parameter, a baseline score of 3 is appropriate.

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 clearly states the verb 'Remove', the resource 'an employer block', and the context 'from get_profile'. It distinguishes from add_blocklist_entry and other remove tools by naming the specific action. Slight ambiguity in 'from get_profile' but overall clear.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like remove_desired_location or remove_desired_title. No prerequisites, conditions, or exclusions are mentioned. The description is purely declarative without usage context.

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

All ApplyAll 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