Skip to main content
Glama
Sign In
Nanites

Nanites

by ADn-001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Role Pin

delete_role_pin

Remove a role pin to revert to dynamic model selection, letting Nanites choose the optimal model for the task.

Instructions

Remove a role pin so that role falls back to dynamic model selection.

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": {
      "role": "<role>"
    },
    "name": "delete_role_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state the behavioral outcome (fallback to dynamic selection), but it does not mention whether removal is permanent, idempotent, or what errors may occur. This adds some context but leaves key undefined behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the action and consequence, with no wasted words. It is concise and readable, though the lack of parameter detail limits its practical value.

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 2 parameters, no annotations, no output schema, and zero schema description coverage, the description is too sparse. An agent cannot tell what 'profile' does, what happens after deletion in detail, or how it interacts with related role pin tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description itself does not explain either the required 'role' parameter or the optional 'profile' parameter. The agent gets no additional meaning beyond the bare schema types, which is inadequate for a tool with multiple parameters.

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?

The description uses a specific verb ('Remove'), a distinct resource ('role pin'), and a clear consequence ('role falls back to dynamic model selection'). It is easily distinguished from sibling tools like set_role_pin and list_role_pins without needing to inspect schemas.

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?

The intended use is implied: use this when you want to remove a role pin and revert to dynamic model selection. However, the description does not explicitly mention alternatives or exclusion conditions (e.g., when to use set_role_pin instead).

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

Deploy Server

Other Tools