Skip to main content
Glama

List dataset pins

argon_pin_list
Read-onlyIdempotent

Lists a project's pins with name, branch, LSN, and note to help you inspect saved database states before merging or discarding changes.

Instructions

List a project's pins (name, branch, LSN, note).

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": {
      "project": "<project>"
    },
    "name": "argon_pin_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the returned field list; it says nothing about pagination, result limits, or behavior when the project has no pins, which are the remaining behaviors an agent would care about.

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?

One short sentence, front-loaded with the verb and resource, with no filler. The parenthetical field list is efficient packaging of return information.

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?

This is a simple read-only, single-parameter tool, so the definition is close to adequate, but with no output schema the description is the only source for return shape and it only names fields without structure or ordering. Missing pagination/empty-result behavior keeps it at minimum viable.

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?

There is a single required parameter with 100% schema description coverage ("Project name"), so the schema already carries the semantics and baseline 3 applies. The description only implies project scoping via "a project's pins" and adds no format or lookup details beyond that.

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 gives a specific verb plus resource ("List a project's pins") and even enumerates the returned fields (name, branch, LSN, note), which clearly separates it from write-side siblings like argon_pin_create or argon_pin_sandbox. It doesn't explicitly name an alternative, so it stops short of full sibling differentiation.

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?

There is no guidance on when to call this versus related tools, nor any stated prerequisites such as whether the project must already be connected or exist. An agent can infer it is the read-side counterpart of pin creation, but the description provides no explicit context or exclusions.

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