Skip to main content
Glama
t3ratech

T3rnel Market Pulse

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MARKET_PULSE_API_KEYNoOptional Market Pulse API key (starts with mpk_). A value that is not a Market Pulse key stops the server at startup, naming the variable.
MARKET_PULSE_BASE_URLNoService origin. Must be https, except http for localhost; no credentials, query or fragment.https://market-pulse.t3ratech.co.zw
MARKET_PULSE_TIMEOUT_MSNoPer-call timeout in milliseconds, between 1000 and 300000.30000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
pulse_lanesA

List the agent-work lanes in the Market Pulse index (bounty boards, agent marketplaces, job feeds, agent networks), each with its evidence-backed grade, liveness, agent-access verdict, freshness and confidence. Use this first to discover lane slugs and to shortlist where an autonomous agent can realistically earn; filters narrow the list and omitting all of them returns every lane. Use pulse_lane_detail for one lane's full record and pulse_should_i_bid for a spend recommendation; use pulse_jobs for individual open listings. Read-only snapshot data, same answer for the same arguments, never changes state. Works without an API key on the free tier. Returns {count, methodologyVersion, lanes[]}; a filter value outside its enum is refused with the values that work, never answered with an empty list.

pulse_lane_detailA

Get the complete record for one agent-work lane: grade and verdict rationale, how an agent accesses it, payout method and currency, adapter, recorded attempts and settlements, and every linked evidence record. Use after pulse_lanes when you need the reasoning behind a grade or the links to act on; do not use it to browse (call pulse_lanes) or to decide whether to spend attempts (call pulse_should_i_bid, which condenses this into a recommendation). Read-only and idempotent. Works without an API key on the free tier. Returns the lane summary fields plus description, website, workUrl, apiUrl, accessMethod, payoutMethod, verdict and an evidence[] array. An unknown slug is refused with an error naming it.

pulse_should_i_bidA

Get a one-call, evidence-backed recommendation on whether an autonomous agent should spend attempts on a lane: one of bid, bid_cautiously, probe_first, avoid or insufficient_evidence, with the rationale and caveats. Call pulse_lanes first to get the slug, then call this before committing an agent's time or an application to any lane; it is the decision tool, while pulse_lane_detail is the audit trail behind it. A recommendation reflects observed outcomes inside the snapshot window, never a guarantee, and Unknown means unmeasured rather than failed. Read-only and idempotent. Works without an API key on the free tier. Returns {lane, grade, confidence, freshness, methodologyVersion, recommendation, rationale, caveats[]}. An unknown lane is refused with an error naming it.

pulse_evidenceA

Read the hash-chained evidence ledger that every grade is derived from: one record by id, every record linked to a lane, or the whole chain when no argument is given. Use it to verify a claim before relying on it, to cite sources, or to audit that a record has not been altered (each record carries payloadSha256, previousChainHash and chainHash). Call pulse_lanes to find a lane slug; pass id or lane, not both; with neither you receive the entire ledger, which is large, so prefer a lane. Read-only and idempotent. Works without an API key on the free tier. Returns {count, records[]} where each record has id, kind, lane, source, captureMethod, capturedAt, summary and the hashes. An unknown id or lane is refused with an error naming it.

pulse_statsA

Get the index's headline numbers: lanes, graded lanes, grade distribution, probes, evidence records, attempts, settlements and settlement value, directory resources, live job count, and the snapshot date they describe. Use it to size the index, to quote a current figure with its date, or to check data freshness before trusting a grade; use pulse_lanes when you need the lanes themselves. Takes no arguments, read-only and idempotent. Works without an API key on the free tier. Returns a flat object including snapshotAt, methodologyVersion, lanes, gradedLanes, grades, settlements and evidenceRecords.

pulse_methodologyA

Get the grading rules themselves: what each grade (A, B, C, F, Unknown) requires, how freshness is derived, how Unknown is handled, and the independence guarantee that money, sponsorship and subscriptions cannot change a grade. Use it to explain or defend a grade to a human, or to interpret the grade filter on pulse_lanes; it describes policy, not any one lane, so use pulse_lane_detail for a specific verdict. Takes no arguments, read-only and idempotent. Works without an API key on the free tier. Returns {version, grades, rules[], independence, snapshotAt, dataset}.

pulse_resourcesA

Search the agent directory of models, MCP servers, frameworks, tools, platforms, work lanes and other resources, filtered by kind, category, capability, tags, free tier or GitHub stars and sorted as you choose. Use it to find what exists (for example free open-source MCP servers with 1000+ stars, or models that do video-gen); use pulse_resource_detail for one entry's full record and pulse_lanes when the question is about earning work rather than tooling. Filters combine with AND; omit all to list everything in the directory. Read-only and idempotent. Works without an API key on the free tier. Returns {count, kinds, resources[]}. An unknown kind, sort or argument is refused with the accepted values, never silently ignored.

pulse_jobsA

List open job listings collected from the agent-accessible lanes, each with title, organisation, URL, reward and currency, bid count, posting time and status. Use it to find work an agent can take now; use pulse_lanes first if you need to know which lanes are trustworthy. Freshness is tiered by the caller's API key: free sees listings once they are up to 24h old, basic 4h, pro and above can trigger a live refresh, and newer listings are counted in redacted rather than shown. Read-only for the caller, though a keyed call consumes one pull from the daily quota and a pro+ call may refresh the live collection. Returns {tier, count, total, redacted, upgrade, upgradeUrl, listings[]}. Fails with a refusal if the persistent store is unavailable.

pulse_resource_detailA

Get the full directory record for one resource: description, kind, capabilities, tags, pricing flag, GitHub stars, links and source. Use after pulse_resources when you have chosen an entry and need its links or metadata; do not use it for work lanes you want to judge (use pulse_lane_detail). Read-only and idempotent. Works without an API key on the free tier. Returns the resource object, with a verdict block when the resource is a graded lane. An unknown slug is refused with an error naming it.

pulse_accountA

Report which Market Pulse tier this connection is served at (free, basic, pro, max or operator), whether an API key was recognised, the daily pull quota and how much of it remains, the freshness that tier buys, and where to upgrade. Call it after pulse_jobs reports redacted listings, when a call is refused for quota, or to confirm a freshly configured key works; it is the only tool whose answer depends on who is asking, and it returns no listings (use pulse_jobs for those). Read-only and idempotent; it consumes one pull when a key is sent and none when anonymous. Returns {tier, authenticated, quotaPerDay, remainingToday, freshness, pricingUrl, accountUrl}. Never returns the key itself.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource+action, and the descriptions explicitly cross-reference each other to prevent misuse (e.g. pulse_lanes for browsing vs pulse_lane_detail for audit vs pulse_should_i_bid for the decision; pulse_resources vs pulse_resource_detail). The stats/methodology/evidence/jobs/account tools are all clearly separated. No meaningful overlap remains.

Naming Consistency5/5

Every tool uses a uniform snake_case convention with a consistent `pulse_` prefix (pulse_lanes, pulse_lane_detail, pulse_resource_detail, pulse_should_i_bid, etc.). List/detail pairs follow a predictable noun pattern. No mixing of conventions.

Tool Count5/5

10 tools is well-scoped for a market-intelligence server: discovery (lanes/resources/jobs), detail lookups, a decision tool, evidence audit, methodology, stats, and account/quota. Each tool earns its place with no obvious redundancy.

Completeness4/5

The read-only lifecycle is well covered: discover lanes/resources/jobs, drill into detail, get a bid recommendation, verify via the evidence ledger, read methodology/stats, and check account quota. Minor gaps exist (no per-job detail lookup or text search over listings), but core workflows have no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues