Skip to main content
Glama
LinkedParticles

Particles

Official
by LinkedParticles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

particle_search

Find all particles that share a given context fingerprint, using a full SHA-256 hash or an 8+ character prefix. Limit results and optionally search across all projects.

Instructions

List particles sharing a context fingerprint.

Args:
    fingerprint: Full 64-char SHA-256 hex or a prefix (≥ 8 chars).
    limit: Maximum particles to return (default 50, capped at 200 to
        keep responses within MCP per-tool-result token caps —
        fingerprint matches share full ``content`` strings).
    all_projects: On a server bound to one project, read the whole
        store instead of that project's view. The result says so. No effect
        on an unbound server.

Returns:
    Dict with ``fingerprint`` (the queried value) and ``particles``
    (list of ``{id, status, content}`` summaries).

Input Schema

NameRequiredDescriptionDefault
limitNo
fingerprintYes
all_projectsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.210.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the 200-result cap and its rationale (fingerprint matches share full content strings, which would blow token limits), and explains that all_projects is a no-op on an unbound server and that the result signals which view was used. Missing only note on ordering or error behavior for a malformed fingerprint.

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?

Front-loaded purpose sentence followed by tightly packed Args/Returns blocks; nearly every line adds information an agent needs. The docstring formatting is slightly heavier than prose would be, but no content is wasted.

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?

Given an output schema exists, the Returns block is a bonus rather than a necessity, and all parameters plus the cap and binding behaviors are covered. The one gap is that 'context fingerprint' is never defined nor is its source named, so an agent without prior knowledge may not know how to obtain one.

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

Parameters5/5

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

Schema coverage is 0% (bare typed properties), yet the description documents all three: fingerprint as full 64-char SHA-256 hex or a prefix of at least 8 chars, limit with default 50 and hard cap 200, and all_projects with its server-binding nuance. This fully compensates for the empty schema.

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?

States a specific verb and resource plus the filtering key: list particles sharing a context fingerprint. This implicitly separates it from particles_list (unfiltered listing) and particle_show (single particle by id), though neither sibling is named.

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?

The mechanism is clear, but there is no explicit 'use this when you have a fingerprint, use X otherwise' routing, and no stated prerequisites for obtaining a fingerprint. Usage must be inferred from the one-line purpose and the all_projects caveat.

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