Skip to main content
Glama

upsert_particle_groups_batch

Batch insert or update particle groups by case-insensitive name matching, letting AI agents sync many groups in one call.

Instructions

Batch insert or update particle groups matching case-insensitively on name.

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": {
      "particle_groups": "<particle_groups>"
    },
    "name": "upsert_particle_groups_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
particle_groupsYesArray of particle groups to upsert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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 disclose the two most important behavioral traits: it both inserts and updates, and matching is case-insensitive on name. It omits what happens on duplicate names within one batch, partial-failure/atomicity behavior, required permissions, and any return information for a mutation.

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?

A single tight sentence that front-loads the operation and follows with the matching rule; every clause earns its place with no filler.

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?

For a one-parameter batch mutation with no annotations and no output schema, the key identity semantics are covered, but an agent cannot predict atomicity, ordering, or what the call reports back about created vs updated records. Adequate but with clear gaps for a write operation.

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 coverage is 100%, so the baseline is 3, but 'matching case-insensitively on name' supplies real semantic meaning about the name field that the schema ('type: string, minLength: 1') does not — it tells the agent how the insert-vs-update decision is made. It still says nothing about the nested description field or array size expectations.

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 gives a specific verb combination ('batch insert or update' = upsert) and resource ('particle groups'), plus the matching key. 'Batch' implicitly separates it from the singular create_particle_group/update_particle_group siblings, though no sibling is named explicitly.

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 only implied by the word 'batch' — an agent can infer this is for multi-record work, but there is no explicit statement of when to prefer this over create_particle_group, update_particle_group, or populate_particle_groups, and no prerequisites or exclusions.

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