Skip to main content
Glama

Yc Rejection

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)

TDQS

A4.4/5.0
Behavior5/5

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

Adds behavioral details beyond annotations: key-value scoping, persistence differences for authenticated vs. anonymous users (24-hour retention). No contradiction with 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?

Four sentences, front-loaded with purpose, every sentence adds value (use cases, scoping, sibling references). No waste.

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?

Complete for a simple store tool: covers usage, behavior, scoping, and sibling pairing. Lacks return value description, but acceptable given no output schema.

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 covers 100% of parameters with descriptions; the tool description adds no additional parameter-level meaning, so 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?

Description clearly states the tool saves data for reuse across sessions, with specific verb (save) and resource (data). It distinguishes from siblings recall and forget by mentioning them explicitly.

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 when-to-use examples (resolved ticker, user preference) and mentions pairing with recall/forget, but does not explicitly state when not to use it.

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

All Yc Rejection 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.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., multiple ask_pipeworx variants and several Polymarket analysis tools. The presence of meta-tools like discover_tools and suggest_questions adds confusion. Distinguishing between tools like entity_profile, compare_entities, and recent_changes requires careful reading of descriptions.

Naming Consistency2/5

Naming conventions are mixed: some use snake_case (ai_visibility_check, ask_pipeworx), others use underscores (compare_entities, deep_research). Prefixes like pipeworx_ and polymarket_ are inconsistently applied, and there is no clear verb_noun pattern across the set.

Tool Count2/5

With 32 tools, the server is heavily over-scoped for its name 'Yc Rejection'. Only one tool directly relates to that domain. The rest constitute a full data platform, making the count far too high for the implied narrow purpose.

Completeness1/5

For a server named 'Yc Rejection', the tool set is severely incomplete: only one tool generates rejection text. There are no tools for application management, review, or related tasks. The actual completeness of the underlying platform is irrelevant given the misleading name.

Resources