Skip to main content
Glama
Sign In
GLPI MCP

GLPI MCP

by USONDIG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_kb_article_visibility_group

Adds a GLPI group to a knowledge base article's visibility settings so its members can access the article.

Instructions

Ajoute un groupe dans la visibilité d'un article KB.

  • groups_id : ID du groupe GLPI

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": {
      "article_id": "<article_id>",
      "groups_id": "<groups_id>"
    },
    "name": "add_kb_article_visibility_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groups_idYes
article_idYes
entities_idNo
is_recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior1/5

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

No annotations are provided, so the description must carry the full behavioral burden. It only says a group is added to an article's visibility and does not disclose mutation side effects, permission requirements, whether existing visibility entries are replaced or appended, or how entities_id and is_recursive affect behavior.

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?

The description is short, front-loaded, and structured with a parameter bullet. It avoids filler, though its brevity is partly due to omitted information rather than disciplined concision.

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?

For a mutation tool with four parameters, no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It omits the required article_id, the optional entity/recursive behavior, and any return or permission context.

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 should compensate. It defines only groups_id as a GLPI group ID, leaving the required article_id and optional entities_id and is_recursive completely unexplained in both schema and 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 states a specific verb ('Ajoute') and resource ('un groupe dans la visibilité d'un article KB'), making the core action clear. It distinguishes itself from profile-visibility siblings by naming a group rather than a profile, but it does not explicitly contrast with update_kb_article_visibility_group.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as update_kb_article_visibility_group or add_kb_article_visibility_profile. Usage is only implied by the tool name and the brief action statement.

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