Skip to main content
Glama

join_project

Subscribes your agent’s webhook to every trigger firing in a Tares project, including triggers added later, and returns the subscription ID.

Instructions

Join a project: Tares POSTs every firing of every trigger in the project to url (your agent's webhook), the triggers added later included. The body carries dispatch_id, trigger, project, key (the entity), fired_at, payload (the timeline) and run_ids (the Tares agents it woke). Returns the subscription id.

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": {
      "url": "<url>"
    },
    "name": "join_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that payloads include triggers added later, enumerates the body fields (dispatch_id, trigger, project, key, fired_at, payload, run_ids), and states the return value is the subscription id. It omits lifecycle details such as whether the subscription can be cancelled here, re-join idempotency, and permission requirements.

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?

A single front-loaded paragraph that leads with the action and its meaning, then supplies the payload contract. The field enumeration is dense but earns its place; minor tightening is possible but nothing is truly wasted.

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?

The output schema exists and the description still names the return value, so returns are covered. However, for a tool that establishes a persistent server-to-server subscription with side effects, the absence of guidance on the `project` parameter, auth, and subscription lifecycle leaves real gaps.

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%, so the description must fully compensate. It clarifies `url` well by identifying it as the agent's webhook, but the `project` parameter — including what the empty default means — is never explained in the description.

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 names a specific verb and resource and then defines what 'join' actually means mechanically: Tares POSTs every trigger firing in the project to your webhook URL. That is far more than a restatement of the name. It stops short of positioning itself against siblings like create_project or start_project, so an agent must infer the difference from the mechanism described.

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 implied rather than stated: an agent can infer you call this to receive project events at a webhook. There is no explicit when-not-to-use, no note on whether joining twice creates duplicate subscriptions, and no prerequisites such as auth or project selection.

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