Skip to main content
Glama
Sign In
AgenticSystemCore

AgenticSystemCore

by andreibesleaga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

compose

Read-only

Computes the AGSC-07 closure algebra over selected item slugs to return closure results from a Markdown knowledge bundle.

Instructions

Run the AGSC-07 closure algebra over a selection of item slugs.

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": {
      "selection": "<selection>"
    },
    "name": "compose"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

readOnlyHint=true is declared and not contradicted, but the description adds essentially no behavior beyond it: it does not say what is computed, whether the operation is deterministic or expensive, or what constitutes a valid selection. 'Closure algebra' hints at a non-trivial computation without explaining it.

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?

One tight, front-loaded sentence with no filler. The only cost is that the brevity is achieved by leaning on an undefined acronym rather than by precision.

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?

With no output schema and no annotations beyond readOnly, the description must explain the operation and its result. It defines neither what the closure algebra produces nor what a slug looks like, which is inadequate for an obscure domain-specific computation.

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

Parameters3/5

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

The single parameter has 0% schema description coverage, so the description carries the burden. It does add meaning by stating the array holds 'item slugs', but gives no slug format, count limits, or ordering semantics.

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

Purpose3/5

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

The description names a distinct operation (run an AGSC-07 closure algebra) and its input (item slugs), so it is not a tautology of the name. However, 'AGSC-07 closure algebra' is undefined jargon with no sibling differentiation against ask/links/propose/read/remember/search, leaving the actual effect opaque.

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 statement of when to use this tool, when not to, or which sibling it competes with. An agent gets no routing signal at all beyond the tool's existence.

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