Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

Check bid fit

check_bid_fit
Read-only

Run a bid/no-bid fit check on a solicitation: five questions scored 0 to 2, for a fit read of Strong fit, Worth a closer look, or Likely pass. This is a fit score, never a win prediction. Needs the solicitation text or file plus a short title, source, and the five answers. Starts an analysis job and returns a result token; call get_bid_check_result with the token to read the verdict. Free, no sign-in.

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": {
      "title": "<title>",
      "source": "<source>",
      "answers": "<answers>",
      "processingConsent": "<processingConsent>"
    },
    "name": "check_bid_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNoSolicitation text, 40 to 100000 characters. Provide text or file.
titleYesShort title for the bid, up to 200 characters.
sourceYesWhere the solicitation came from, up to 500 characters.
answersYes
processingConsentYesMust be true: confirms the source may be processed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the lone readOnlyHint annotation by disclosing the async execution model ('Starts an analysis job and returns a result token'), the required follow-up call, and the cost/auth profile ('Free, no sign-in'). It also bounds the semantics of the score itself ('never a win prediction'), which is the single most important behavioral caveat for an agent interpreting the result.

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?

Five short sentences, front-loaded with what the tool produces before describing inputs and the follow-up call. Every sentence carries distinct information – scope bound, output categories, inputs, job/token behavior, cost – with no repetition of the title.

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 tool with nested objects, a consent flag, and an async token pattern and no output schema, the description still covers output shape (three named verdicts), input requirements, and the retrieval step. Nothing material is missing for an agent to invoke it and then correctly follow up.

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 67% schema coverage and nested objects, the description usefully restates the input contract as 'solicitation text or file plus a short title, source, and the five answers', making the text-vs-file alternative and the five-answer bundle legible at a glance. It adds nothing about the enum values (eligibility, performance, evidence) which are undocumented in the schema, so it does not fully compensate for the coverage gap.

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 ('Run a bid/no-bid fit check on a solicitation') and enumerates the exact output taxonomy (Strong fit / Worth a closer look / Likely pass). It also carves out the scope ('This is a fit score, never a win prediction'), which no sibling result-fetching tool claims, so an agent can separate it from get_bid_check_result 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?

Gives clear operational context: preconditions ('Needs the solicitation text or file plus a short title, source, and the five answers'), a scope exclusion ('never a win prediction'), and an explicit next step ('call get_bid_check_result with the token to read the verdict'). It stops short of saying when NOT to run a fit check (e.g. solicitation already shredded, or no decision deadline), so it falls one step short of full alternative routing.

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

All TenderCrest AI 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