Skip to main content
Glama

SALT19 Agent Utility Grid

by io.github.GabrielAllit1

Sec Company Facts

sec-company-facts
Idempotent

Return selected latest SEC XBRL company facts from EDGAR's live companyfacts feed with source dates and units. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYes
conceptsNo
_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

A3.6/5.0
Behavior4/5

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

The description adds valuable behavior beyond annotations: it discloses the $0.01 x402 price, the 'live' nature of the feed, the presence of source dates and units in the result, and the recommended optional operation id. It does not detail retry/challenge flow, but the schema already documents the payment-signature field.

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, front-loaded sentences: function first, then cost and x402 compatibility guidance. Every sentence earns its place and no filler is present.

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, live-data retrieval tool with no output schema, the description gives the price, the payment method, the output ingredients, and the optional operation id. The schema covers the required cik and payment chaining fields. A remaining gap is the lack of explicit linkage between 'selected facts' and the concepts parameter, but an agent can still invoke the tool correctly.

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?

With schema_description_coverage at 60%, the schema already explains the x402/payment parameters, and the description reinforces operation-id usage. However, the description does not explicitly map 'selected' to the concepts parameter or explain CIK/concept selection behavior beyond the schema constraints.

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 states a clear verb and resource: return selected latest SEC XBRL company facts from EDGAR's live companyfacts feed, including source dates and units. It is specific enough to distinguish from sec-recent-filings, but it never explicitly names alternative siblings, so it stops short of full 5.

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 guidance about when to choose this tool versus sec-recent-filings or the other fact-lookup tools. The description implies its niche through the 'companyfacts' wording but offers no exclusions, prerequisites, or alternative-selection logic.

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