Skip to main content
Glama

Check program fit

check_program_fit
Read-onlyIdempotent

Runs the same matching rules as emergenttechnologies.ai/fit on a person's answers and says which kind of program fits (data licensing, the referral partner program, or expert work) and why. It collects and saves nothing and takes no personal details. To see their specific route and proceed, the person continues at /fit, where they enter their own details with consent.

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": {
      "path": "<path>"
    },
    "name": "check_program_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYescompany = owns or runs a company; closed = the company closed; professional = lawyer, doctor, accountant, exec; partner = brings deals
roleNoProfessional path
reachNoPartner path: how many companies they can reach
toolsNoSystems the company uses; paper = mostly paper
yearsNoYears of records: lt3, 3to5, 5to10, 10plus
servesNoWho the company mostly serves
statusNoCompany path: is it still operating?
countryNous; ca_uk_au = Canada, UK or Australia; other
industryNoThe company's industry: legal, accounting_finance, medical, or other for any other industry (for example, software and IT services, HVAC, manufacturing or logistics)
interestNoCompany paths: license = license the records; refer = offer this to clients; both
languageNoLanguage of most records
licensedNoProfessional path: licensed in their field?
dataTypesNoSpecialised records the company holds, such as CAD files, source code repositories or simulation and sensor logs; none if it holds none
employeesNoPeople at the company (at its peak if closed)
partnerTypeNoPartner path
industryDetailNoWhen industry is other

Output Schema

NameRequiredDescriptionDefault
whyYes
fitsYes
metaYes
routeYes
capturedYes
programsYes
continueAtYes
whatHappensThereYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is largely covered. The description still earns credit for stating that nothing is collected or saved and no personal details are taken, plus the consent-based handoff to /fit. It says nothing about how a result is chosen or what the response looks like, though an output schema exists.

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 short sentences, front-loaded with what it does, then privacy, then the handoff. Nothing is redundant or buried.

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?

Privacy posture, purpose, and the follow-up path are all covered, and the output schema plus full parameter descriptions handle return shape and enum meaning. Minor gap: no indication of behavior when required path is ambiguous or answers are insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage and 14 enum parameters, the schema carries the semantics and a baseline 3 would apply. The description adds a little by framing inputs as "a person's answers" and naming the three outcome programs, orienting the agent to what the enums select for, without explaining path-relevance (e.g. that role only matters for professional and reach only for partner).

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 names a specific operation (runs matching rules on a person's answers) and a concrete output (which of three program kinds fits, and why), which lets an agent distinguish it from siblings like partner_program or consulting_offer without opening a schema.

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?

It makes the context of use clear: a qualification step whose follow-through happens at /fit, where the person supplies their own details. It does not explicitly rule out sibling tools or state prerequisites for calling it, so the agent must infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.