Skip to main content
Glama
Sign In

ATTIM

by link.attim
OverviewDiscussionsAdmin

List links

list_links
Read-onlyIdempotent

List the links on a profile or link page with their ids, pinned first, and the position visitors see.

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": {
      "slug": "<slug>"
    },
    "name": "list_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
slugYes
smartYes
pinnedYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / slug / minLength
      Removed value: -1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "link": {
+      "properties": {
+        "disabled": {
+          "type": "boolean"
+        },
+        "group": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "section": {
+          "type": "string"
+        },
+        "trackingEnabled": {
+          "type": "boolean"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "label",
+        "url"
+      ],
+      "type": "object"
+    }
+  },
+  "properties": {
+    "pinned": {
+      "items": {
+        "$ref": "#/$defs/link"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "smart": {
+      "items": {
+        "$ref": "#/$defs/link"
+      },
+      "type": "array"
+    },
+    "version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "slug",
+    "version",
+    "pinned",
+    "smart"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are ordered with pinned links first and include the visitor-visible position. It omits pagination, result-count limits, and error behavior for an unknown slug, so it is additive but incomplete.

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 sentence, front-loaded with the verb and resource, with the ordering guarantee appended rather than buried. No filler or redundant restatement of the title.

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?

An output schema exists, so return-value detail is not required, and the tool is a simple read-only list with one parameter. Still, for an agent to call it correctly the description should clarify what "slug" refers to and whether the result set is capped, which it does not.

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 0% for the single required parameter "slug", so the description carries the burden. Saying links live "on a profile or link page" implies the slug identifies that page, but it never states the slug format, where to obtain one, or whether short names and usernames differ. Partial compensation only.

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 specific verb and resource ("List the links") plus the scope ("on a profile or link page"), so an agent can distinguish it from mutation siblings like set_links. It does not explicitly contrast with other read siblings such as get_link_stats or get_profile, which keeps it short of a 5.

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: the phrase "with their ids, pinned first, and the position visitors see" hints that this is the call for ordered link inventories, but there is no explicit when-to-use, when-not-to-use, or named alternative. Alternatives are left entirely to inference from sibling names.

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

All ATTIM toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources