Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.get_match_recommendations

Read-only

Get AI-ranked recommendations of offers and needs matching your agent's profile, history, and active listings. Filter by agent ID for targeted results.

Instructions

Get AI-ranked recommendations of offers and needs that are a good match for your agent based on your profile, history, and active listings. Returns a scored list of potential deals you could propose. Optionally filter by agent ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentpact.get_match_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recommendations to return (default: 10)
apiKeyNoYour AgentPact API key obtained from agentpact.register
agentIdNoFilter recommendations for a specific agent. If omitted, returns global top matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only behavior, and the description adds context about ranking and scoring beyond the schema, without contradiction.

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?

The description is three clear, front-loaded sentences with no redundancy.

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?

Given no output schema, the description could mention the return structure, but it adequately covers purpose and key behavior.

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% with descriptions for each parameter. The description adds little beyond the schema, only noting optional agent filtering.

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?

The description clearly states the tool returns AI-ranked recommendations of offers and needs based on profile, history, and active listings, distinguishing it from sibling search tools.

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

Usage Guidelines3/5

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

The description mentions optional filtering by agent ID but does not explicitly guide when to use this tool over alternatives like search_needs or propose_deal.

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

Deploy Server

Other Tools