Skip to main content
Glama

H1b

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds scoping detail and listing behavior, which is useful but not essential beyond annotations.

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 sentences with no fluff. First sentence states main purpose; second adds usage advice. Perfectly front-loaded and concise.

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?

Adequately describes tool behavior given low complexity, no output schema, and rich annotations. Could mention return format, but not essential.

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 100% and schema already describes the parameter. Description reinforces schema without adding new semantics. Baseline score of 3 is appropriate.

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?

Clearly states the tool retrieves a saved value or lists keys. Differentiates from sibling tools 'remember' and 'forget' by explicitly pairing with them.

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?

Provides clear context for when to use the tool (look up previously stored context) and mentions scoping, but does not explicitly exclude alternative tools or scenarios.

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

All H1b 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.1/5.0
Disambiguation3/5

Several overlapping clusters exist: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all handle research questions, polymarket_edges and polymarket_arbitrage both scan for trading opportunities, and discover_tools/suggest_questions serve similar discovery purposes. The long, use-case-specific descriptions help, but an agent could still easily pick the wrong tool among these near-duplicates.

Naming Consistency4/5

Most tools follow a snake_case verb_noun or noun pattern (resolve_entity, validate_claim, list_subscriptions, h1b_salary), which is fairly consistent. However, there are deviations: bare verbs like recall/remember/forget/subscribe, noun-only phrases like entity_profile and recent_changes, and the ask_pipeworx_beta suffix variant break the pattern slightly.

Tool Count2/5

34 tools is well past the 25+ threshold, and the server is named 'H1b' while only 3 of the 34 tools relate to H-1B data. The rest is a sprawling mix of data research, prediction-market analytics, memory, subscriptions, AI visibility checks, and unrelated utilities like generate_llms_txt and scan_dependency — a severe scope mismatch.

Completeness4/5

As a de facto Pipeworx research platform, the surface is nearly complete: open-ended queries, grounded evidence mode, deep multi-source research, entity resolution, comparison, claim validation, subscriptions, memory, and feedback. The H-1B sub-domain covers employer, salary, and top-sponsor lookups, though the mention of green cards is a small mismatch since only LCA data is provided.

Resources