Skip to main content
Glama
Sign In
agent-nexus

agent-nexus

by dugubuyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_subscription

Add a subscription rule to notify a subscriber project about changes to a specific document or all documents of a given type.

Instructions

Add a subscription rule. Provide target_doc_id for exact doc or target_doc_type for all docs of that type.

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": {
      "subscriber_project_id": "<subscriber_project_id>",
      "project_space_id": "<project_space_id>"
    },
    "name": "add_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriber_project_idYes
project_space_idYes
target_doc_idNo
target_doc_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It implies a creation operation ('Add') but lacks details on side effects, permissions, idempotency, or what happens if a subscription already exists. The description is minimal and does not adequately inform the agent of behavioral constraints.

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?

The description is extremely concise, consisting of a single sentence that conveys the core purpose and usage of the two key parameters. No unnecessary words or repetition.

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

Completeness2/5

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

Given the tool has 4 parameters, no output schema, and no annotations, the description should provide more context. It only partially explains two parameters and omits the required ones. There is no mention of return values, error conditions, or typical use cases, making it incomplete for an AI agent to reliably use.

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

Parameters2/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 compensate. It explains target_doc_id and target_doc_type, but the required parameters subscriber_project_id and project_space_id are left unexplained. This leaves a significant gap in understanding the tool's input requirements.

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 clearly states 'Add a subscription rule', specifying the verb and resource. It also distinguishes between targeting a specific document or all documents of a type, which helps differentiate from sibling tools that don't involve subscriptions. However, the concept of 'subscription rule' is not further explained, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance on when to use each targeting parameter: 'Provide target_doc_id for exact doc or target_doc_type for all docs of that type'. This is clear context for usage. However, it does not mention when not to use the tool or compare to alternatives, though sibling tools are not directly related.

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

Deploy Server

Other Tools