Skip to main content
Glama

Greenhouse

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds persistence details (scoped by identifier, 24-hour retention for anonymous) beyond annotations. No contradictions; annotations already declare idempotent and non-destructive.

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?

Three concise sentences: purpose first, then usage, then persistence details. No wasted words; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully explains storage mechanism, scoping, retention, and companion tools, making it complete despite lack of output schema and simple parameters.

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 already covers both parameters (key, value) with descriptions. The description adds example values but no new semantic depth beyond schema.

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 verb ('save') and resource ('data as key-value pair'), with specific examples of what to store. Distinguishes from sibling tools by mentioning recall and forget.

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

Usage Guidelines5/5

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

Explicitly tells when to use ('when you discover something worth carrying forward') and pairs with related tools ('recall', 'forget'), providing clear guidance.

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

All Greenhouse 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

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes with detailed descriptions, but some overlap exists between research tools like ask_pipeworx, deep_research, and bet_research, which could confuse an agent. The Greenhouse-specific tools are clearly separated by the 'greenhouse_' prefix, aiding disambiguation.

Naming Consistency3/5

Tool names follow snake_case but vary in style: some have a prefix like 'greenhouse_' or 'pipeworx_', others do not (e.g., ask_pipeworx vs. deep_research). The verb-object pattern is inconsistent (e.g., 'generate_llms_txt' vs. 'entity_profile'), making naming less predictable.

Tool Count2/5

35 tools is excessive for a single server, especially one named 'Greenhouse' which implies an ATS focus. The set aggregates multiple domains (ATS, data research, memory, prediction markets) without clear scoping, overwhelming the agent and reducing coherence.

Completeness3/5

The Pipeworx/data research subset is fairly complete with lookups, comparisons, verification, and subscriptions. However, the Greenhouse ATS subset lacks create/update/delete operations, leaving notable gaps. The mixed domains make overall completeness uneven.

Resources