Skip to main content
Glama
Sign In

Cofounderbase: AI automation agencies

by io.github.Rupesh7128
OverviewDiscussionsAdmin

Match the best 5 agencies to a project

match_agencies
Read-only

Describe a project and get exactly the 5 best-fit agencies, each with a one-line reason. Verified agencies receive a ranking boost in this tool. Optional budget (USD) and location (city or country).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_brief": "<project_brief>"
    },
    "name": "match_agencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetNoMax budget in USD, e.g. 5000 or "$5k"
locationNoCity or country the agency should be based in
project_briefYesWhat needs to be built, e.g. "WhatsApp support bot for a Spanish e-commerce shop"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: a fixed result count of 5, a one-line justification per agency, and a disclosed ranking bias toward verified agencies. It stops short of saying what happens when fewer than 5 matches exist.

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 tight sentences: the outcome and result shape come first, then the ranking caveat, then optional inputs. Nothing is padded and no sentence is redundant.

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?

For a read-only, non-open-world tool with no output schema, the description supplies the essentials: what it returns, how many, and the ranking bias. The only gap is edge-case behavior (fewer than 5 matches, empty results) which an agent might reasonably want before committing.

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 description coverage is 100%, so the schema already explains all three parameters including budget formats and location scope. The description only restates that budget is USD and location is city/country, adding no interpretation guidance such as how budget affects matching. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('match_agencies' / 'Describe a project and get exactly the 5 best-fit agencies') with a fixed result cardinality and per-result rationale. It clearly differs in spirit from search_agencies and top_agencies, but never names those siblings to make the boundary explicit.

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?

Usage is implied by 'Describe a project' plus the note that budget and location are optional, so an agent can infer this is the semantic/shortlist path. There is no explicit when-to-use vs search_agencies/top_agencies guidance and no exclusions or prerequisites.

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

All Cofounderbase: AI automation agencies toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources