Skip to main content
Glama

validate_submission

Read-onlyIdempotent

Check founder-approved project details against the existing intake schema without saving or sending an application. Does not return the applicant’s personal details.

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": {
      "submission": "<submission>"
    },
    "name": "validate_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
submissionYesAll strings are trimmed. Agent submissions must set submitted_by.founder_authorized=true after the founder approves review and follow-up. No eligibility restrictions on stage, sector or country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds genuine value: it confirms nothing is persisted or sent and discloses a privacy trait ('does not return personal details'). These are real behavioral facts beyond the structured hints.

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 with zero waste, and the no-persistence constraint is front-loaded where it matters most for a read-only dry-run.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a validation tool with no output schema, the description tells the agent what it does NOT return (personal details) but never says what it DOES return—validation errors, a pass/fail flag, a normalized object. That missing return-shape cue is a meaningful gap for a single deeply-nested input.

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?

With 100% schema coverage, the heavily-annotated nested schema already documents the trimming rules and the submitted_by.founder_authorized requirement. The description adds no parameter-level meaning beyond it, so the baseline 3 for schema-driven coverage 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?

States a specific verb (check/validate) and resource (project details against the intake schema), and the phrase 'without saving or sending an application' clearly separates it from its write sibling submit_project. It stops short of naming the siblings explicitly, but an agent can infer the read-only validation role.

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 'founder-approved' precondition and 'without saving or sending' phrasing imply this is a dry-run to run before submit_project, so usage is inferable. However, it never explicitly says 'use this before calling submit_project' or states when to prefer it, leaving the routing to inference.

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.