Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Create Tag Tool

create-tag-tool

Create a new tag for a project. Requires a name (unique per project, case-insensitive, so sending a duplicate in any casing returns an error) and a color from the preset palette.

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_id": "<project_id>",
      "name": "<name>",
      "color": "<color>"
    },
    "name": "create-tag-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe tag label (max 64 characters). Names are unique per project, case-insensitive, so "Branded" and "branded" collide.
colorYesThe tag color. Must be one of: gray, red, orange, amber, green, teal, blue, indigo, violet, pink.
project_idYesThe numeric id of the project the tag belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the uniqueness constraint and, importantly, the failure mode: a case-insensitive duplicate returns an error. It doesn't mention permissions or what the created tag looks like, but the error semantics are the most useful thing an agent could know here.

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?

Two tight sentences with the resource stated first and constraints second, and no filler. The parameter recap is slightly redundant against a fully-documented schema, which keeps it from a 5.

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

Completeness4/5

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

A simple three-parameter create tool with annotations and a fully described schema needs little more than what's here. The error-on-duplicate behavior and project scoping cover the main edge cases; only permission requirements are left unstated.

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%, and the schema already states the case-insensitive collision rule for name and enumerates the color palette. The description's parameter detail is essentially a restatement, so baseline 3 applies rather than credit for added meaning.

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+resource ('Create a new tag') and scopes it to a project, so it's clearly distinct from update-tag-tool or delete-tag-tool. It doesn't explicitly name a sibling, so it stops short of full differentiation.

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 project-scoping context implies when the tool applies, but there's no explicit when-to-use versus when-not guidance, no mention of how to resolve duplicates (e.g., use update-tag-tool instead), and no stated prerequisites such as project permissions.

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

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