Skip to main content
Glama
Sign In

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

tascan_create_project

Create a new TaScan project (top-level container for events). number is optional (the next P-number is assigned when omitted; a number already used in the org is refused 409). external_refs links customer job numbers.

Input Schema

NameRequiredDescriptionDefault
nameYesProject name
numberNoProject number, 1-40 letters, digits, dot, underscore or hyphen, unique in the org (default: next P-00001 style number). P-<digits> numbers are assigned automatically and refused 400 here; use your own format (e.g. P14-4680)
locationNoProject location / venue
external_refsNoUp to 10 external references, each { source (1-40 chars, e.g. "EEQ"), ref (1-80 chars, e.g. "P14-4680") }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / external_refs
      Added value: +{
+  "description": "Up to 10 external references, each { source (1-40 chars, e.g. \"EEQ\"), ref (1-80 chars, e.g. \"P14-4680\") }",
+  "items": {
+    "properties": {
+      "ref": {
+        "type": "string"
+      },
+      "source": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "source",
+      "ref"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / number
      Added value: +{
+  "description": "Project number, 1-40 letters, digits, dot, underscore or hyphen, unique in the org (default: next P-00001 style number). P-<digits> numbers are assigned automatically and refused 400 here; use your own format (e.g. P14-4680)",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare the write/creation safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description carries a lower burden. It adds genuinely useful behavior beyond annotations: the next P-number is auto-assigned when 'number' is omitted, and a duplicate number is refused with 409. It does not mention auth requirements or the shape of the created object.

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?

Three tight sentences, front-loaded with the core action and entity role, then the optional-parameter default/conflict behavior, then the external_refs purpose. No redundant restatement of the tool name or schema details.

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?

With write annotations present and no output schema, the description covers the essentials for a create tool: default value behavior, the 409 conflict case, and the semantics of the non-obvious parameter. Missing only the return payload and permission/scope requirements, which are minor gaps for this complexity level.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning over the schema for two parameters: it explains that 'number' is optional with a server-assigned default and that 'external_refs' links customer job numbers, an intent not captured in the schema text. That is value beyond what the structured fields provide.

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?

States a specific verb and resource ('Create a new TaScan project') and immediately clarifies the entity's role ('top-level container for events'), which distinguishes it from the sibling tascan_create_event. An agent can tell what this tool produces without opening the schema.

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 context is implied by the 'top-level container for events' framing, which tells the agent this is the parent object to create before events. However, there is no explicit when-to-use statement, no mention of prerequisites (e.g. org membership), and no named alternative, so guidance remains inferred rather than stated.

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

All TaScan toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources