Skip to main content
Glama

Corply — Start and run your company

by io.github.corply-dev
OverviewDiscussionsAdmin

Start a document-based import

create_import_intake

Open a document dump for importing an existing company: returns an upload page (uploadUrl) and an upload-only endpoint for your shell (curlExample). No company details are needed first. Start an existing-company import from the founder's documents instead of asking for details they already have on paper. Call create_import_intake, then either open or present uploadUrl for the founder to drop every formation PDF they have, or, when the files are on this machine, upload them from your shell with curlExample (one -F file=@path per file; never paste PDF contents into a tool call). Founder-provided public PDF links go through add_import_intake_url. Then call read_import_intake until remaining is 0. Show reviewMarkdown verbatim: any Checks to accept, the Looks right table, then the Needs a look table. When it lists Checks to accept, ask about each one before confirming: the founder either changes a value or explicitly accepts it as is; pass the keys they accepted in acknowledgedIssues (confirmation is refused while any check is unanswered). Then ask ONE native multiple-choice question: "Confirm and import (default)" first, then "Change a value". Pressing Enter on the default is the founder's confirmation; only then call confirm_import_intake with the reviewHash. For a change, ask which value and the new value, and pass it in values keyed by the row key. Never confirm without that answer. Confirming creates the import from the confirmed values; a Corply reviewer still reviews each document. Afterwards present the missing items one multiple-choice question at a time, using each item's note. Prerequisite: authenticated active company access plus every prerequisite stated above. Canonicality: invokes the shared backend action; trust the returned actual_tool_output and context_engineering instead of adding a state-recovery call. Idempotency: obey the tool-specific retry key or guarantee; if none is stated, inspect refreshed state before retrying. Confirmation boundary: no additional confirmation is needed for this read, reversible save, explicit fact/evidence record, link preparation, plan refresh, or action pre-authorized by a standing founder-configured policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_corply_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior1/5

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

Annotations declare readOnlyHint=false, but the description says 'no additional confirmation is needed for this read,' implying a read-only operation. That directly contradicts the annotation, which marks this as not read-only. The rest of the description is rich, but this inconsistency forces a 1 under the rubric.

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

Conciseness2/5

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

Purpose is front-loaded, but the description is bloated with downstream-tool instructions, generic boilerplate about canonicality, idempotency, and confirmation boundaries. Much of this does not help an agent select or invoke create_import_intake correctly.

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?

Given the absence of an output schema, the description does explain returned artifacts like uploadUrl and curlExample. It also covers prerequisites and the broader import workflow. It falls short on the one parameter and contains misleading confirmation-boundary language, so it is not fully complete.

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

Parameters1/5

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

Schema description coverage is 0%, and the only parameter is the nested _corply_context object with id and receipt fields. The description never mentions or explains this parameter, so it adds no meaning beyond the schema and does not 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: 'Open a document dump for importing an existing company' and 'Start an existing-company import from the founder's documents.' It clearly distinguishes this intake-creation step from siblings like add_import_intake_url, read_import_intake, and confirm_import_intake.

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?

Explicitly says to use this instead of asking for company details, then gives the conditions for opening uploadUrl vs. shell uploads via curlExample, and routes public PDF links to add_import_intake_url. It also prescribes the subsequent read_import_intake and confirm_import_intake flow.

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

All Corply — Start and run your company 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