Skip to main content
Glama
Sign In
Nanites

Nanites

by ADn-001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Role Pins

list_role_pins

Shows which models are pinned to each role for a profile, defaulting to the active profile. Use it to review current role-to-model assignments.

Instructions

List the role->model pins for a profile (default active).

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

Input Schema

NameRequiredDescriptionDefault
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description itself must convey safety and behavior. 'List' implies a read-only operation and 'default active' adds useful behavior, but it does not disclose response format, whether an invalid profile produces an error, or any ordering/filtering behavior.

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?

A single, front-loaded sentence with no wasted words. It communicates the operation, the resource, the profile scope, and the default behavior efficiently.

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

Completeness3/5

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

For a simple read tool with one optional parameter, the description is mostly sufficient for invocation. However, with no output schema and no mention of return values or error behavior, an agent is left to guess what the tool actually returns beyond a vague idea of a pin listing.

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?

The schema only defines 'profile' as a string with minLength 1 and 0% description coverage. The description adds the key meaning that the parameter is optional and defaults to the active profile, but it does not clarify what identifier values are expected (name vs. id) or how it relates to switch_profile.

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?

States a clear verb ('List') and a specific resource ('role->model pins'), and notes the profile scope. It is easy to distinguish from sibling mutation tools like set_role_pin and delete_role_pin, though it does not explicitly name any alternative.

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 about when to use this tool versus alternatives such as list_models or the pin mutation tools. The 'default active' note gives some context, but the description does not state when this tool is the right choice or when another tool should be used.

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