Skip to main content
Glama

pscale-biome

by io.github.pscale-commons

meet

Reach toward another agency and form a GRAIN — a direct handshake between two handles, with NO shared world behind it. This is the lens pointed not at a substrate but at another mind: you post your reach (what you offer or say this turn) and read theirs back; when both sides have reached, the grain is FORMED. It lives only in the meeting (an ephemeral channel) — never written to any beach, never persisted; it evaporates when either of you leaves. The other party must also call meet (naming you) for the handshake to form. Runs NO model and touches no storage — you bring the meaning. To KEEP what you agreed, write it into your own shell with spark, deliberately. Be transparent — narrate your calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faceNoYour aperture in the meeting (character / author / designer / observer). Default character.
withYesWho you are reaching toward — their handle. They must meet you back for the grain to form.
reachNoYour offering this turn — what you say, propose, or hold out to the other. Omit to ping presence without words.
handleYesWho you are — your handle.

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: no model runs, no storage touched, ephemeral channel that evaporates when either leaves. Includes instruction to 'Be transparent — narrate your calls,' adding ethical context.

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 detailed and front-loaded, but some sentences could be tightened. Nonetheless, every sentence serves a purpose, and the structure flows logically from purpose to lifecycle to advice.

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

Completeness5/5

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

Given no output schema, the description covers all necessary aspects: purpose, lifecycle, prerequisites, alternatives, and behavioral constraints. It fully prepares an agent to use the tool correctly.

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?

All 4 parameters have schema descriptions (100% coverage). The description adds narrative meaning, e.g., 'your aperture in the meeting' for face and 'your offering this turn' for reach, enhancing understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: forming a direct handshake between two handles without a shared world. It distinguishes from siblings by emphasizing no model runs and no storage, making its unique function explicit.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use the tool (to connect with another agent) and prerequisites (other party must call meet). Also advises on alternative action (use spark to persist agreements) and calls for transparent narration.

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

All pscale-biome toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: meet is ephemeral agent-to-agent communication, play is turn-based RPG interaction, and spark is reading/writing a public commons. The descriptions are detailed enough to avoid confusion.

Naming Consistency5/5

All tool names are single verbs (meet, play, spark), following a consistent pattern of imperative style and lowercase. No mix of conventions.

Tool Count4/5

With only 3 tools, the server is on the lower end of the reasonable range. However, each tool represents a core function and the count is still within the typical 3-15 range, so it is slightly under but acceptable.

Completeness4/5

The tools cover essential operations: ephemeral handshake, RPG turn-playing, and commons read/write. However, explicit delete or list operations for the commons are missing, but spark's write may subsume updates. Minor gap.

Resources