Skip to main content
Glama

SALT19 Agent Utility Grid

by io.github.GabrielAllit1

Github Repo Facts

github-repo-facts
Idempotent

Return current public GitHub repository facts such as archive state, license, stars, forks, branch and latest push without the premium adoption decision. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYes
_salt19_handoff_idNoOptional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry.
_salt19_operation_idNoOptional but recommended semantic purchase identifier preserved across challenge/payment/retries.
_x402_payment_signatureNoOptional x402 payment proof. Omit on the first call; include after satisfying the challenge.

TDQS

A4.2/5.0
Behavior4/5

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

The description adds useful behavior beyond annotations: the $0.01 x402 price, reliance on current external repo state, and recommendation of _salt19_operation_id. Although readOnlyHint is false, the description does not claim to be purely read-only; the paid x402 flow explains the side effect. No annotation contradiction.

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?

Two tight sentences: the first front-loads purpose and scope, the second conveys pricing and payment compatibility guidance. No filler or redundant restatement of the title.

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?

For a paid facts-retrieval tool, it covers the core purpose, data scope, example facts, cost, and x402 operation-id hint. With no output schema, the listed facts provide a rough return-shape expectation. Minor gaps remain around repo format and error behavior.

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?

Schema coverage is 75%, so most parameters are already described. The description mostly restates the optional/recommended nature of _salt19_operation_id but does not compensate for the undocumented required repo parameter, such as expected format or examples.

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?

States a specific verb and resource: 'Return current public GitHub repository facts', with concrete examples like archive state, license, stars, forks, branch, and latest push. The phrase 'without the premium adoption decision' further distinguishes it from decision-oriented sibling tools.

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

Usage Guidelines4/5

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

Clearly frames the intended use: retrieving basic public GitHub facts rather than making an adoption decision. It does not explicitly name alternatives like repo-adoption-go-no-go, but the exclusion is clear enough to route most agents.

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

All SALT19 Agent Utility Grid 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

B3.4/5.0
Disambiguation2/5

Multiple tools occupy the same decision space: agent-decision-preflight, dependency-go-no-go, repo-adoption-go-no-go, github-repo-preflight, and npm-package-intel all target install/adopt GO/WARN/BLOCK decisions with overlapping scope. Discovery tools like find-salt19-tool and salt19-pricing also blur together. Descriptions are detailed, but the boundaries between these tiers are not obvious enough for reliable agent selection.

Naming Consistency3/5

Names consistently use lowercase hyphenated tokens and domain prefixes, which gives some predictability. However, styles are mixed: some tools are verb-led (find-, report-, verify-), while others are noun-headed (github-repo-facts, salt19-pricing, nws-active-alerts), and product-tier suffixes like -preflight, -facts, -intel, and -go-no-go are applied inconsistently. The naming is readable but does not follow a single clear pattern.

Tool Count2/5

33 tools is well above the range where a toolset remains easy to navigate, even for a broadly scoped utility grid. The count includes multiple free routing/telemetry tools plus many paid data and decision tools, making the surface feel heavy. A more consolidated tiered design would reduce selection burden.

Completeness4/5

The server covers a wide range of claimed capabilities: live state/facts for Base, GitHub, npm, SEC, NWS, USGS, and URL; bounded decisions for dependencies, repos, plans, code changes, and commerce; plus x402 payment support and receipt verification. Minor gaps exist around actually executing payments or settlements, but that seems intentionally out of scope for a non-custodial utility grid.

Resources