Skip to main content
Glama

Read a match

readMatch
Read-onlyIdempotent

One of the candidate's matches in full, by the opportunityId from listMatches or listMyPipeline: the role description, tech stack, experience band, visa line, interview stages, the company block, and every role question with its current answer.

Use it before likeMatch or declineMatch when the row alone is not enough, and to help draft answers for answerRoleQuestion. Refuses an opportunityId that is not the candidate's own. Open roles from listMatches (kind open_role) have no opportunityId yet; readJobListing with their jobId has the full role.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "opportunityId": "<opportunityId>"
    },
    "name": "readMatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
opportunityIdYesThe opportunityId from listMatches or listMyPipeline.

Output Schema

NameRequiredDescriptionDefault
kindYes
visaYes
jobIdYes
reasonYes
salaryYes
statusYes
companyYes
locationYes
positionYes
whyMatchYes
createdAtYes
questionsYes
techStackYes
experienceYes
arrangementYes
companyNameYes
descriptionYes
referralUrlYes
partnerLabelYes
interviewDateYes
matchStrengthYes
opportunityIdYes
applyOwnershipYes
introRequestedYes
interviewStagesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered; the description adds real context beyond that by disclosing the ownership check (it refuses an opportunityId that is not the candidate's own) and a privacy/logging note about recorded inputs and results. The only shortfall is that it does not describe return format or size, which the output schema partly absorbs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the parameter's origin, then the usage routing, then the edge case, then the privacy note — a sensible ordering. The enumerated content list is long but informative; the trailing data-recording sentence is boilerplate that costs a little density.

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?

For a one-parameter read tool with an output schema and rich annotations, the description covers what it returns, when to call it, its sibling alternatives, and its failure mode (non-owned opportunityId). An agent has everything needed to select and invoke it correctly.

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 a single parameter at 100% schema coverage, the schema already documents the field, and the description largely restates its provenance (from listMatches or listMyPipeline). It does add meaning beyond the schema by warning that open_role rows from listMatches carry no opportunityId at all, which tells the agent when this parameter cannot be supplied.

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?

States a specific verb and resource — reading one candidate's match in full, keyed by opportunityId — and enumerates exactly what comes back (role description, tech stack, experience band, visa line, interview stages, company block, role questions with answers). It is clearly separable from listMatches/listMyPipeline (listing) and readJobListing (open roles without an opportunityId).

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?

Gives explicit when-to-use guidance: before likeMatch or declineMatch when the row alone is insufficient, and for drafting answers for answerRoleQuestion. It also names the alternative for the edge case — open_role entries have no opportunityId yet, so use readJobListing with their jobId instead.

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.

Resources