Winquill

Save company profile

save_company_profile

DestructiveIdempotent

Use this when the user wants Winquill to remember their business for searches, fit and readiness checks and drafting. Fill in only company facts the user has told you, leaving out anything unsure and any personal details, and show the user what you'll save so they can confirm or correct it first. Saves to their team's workspace and fills in more from Companies House (SAM.gov for a US company) and contracts the company has won. Needs a Winquill account. Not for personal profiles or CVs. Example: {"summary":"Office and school cleaning in Greater Manchester","company_number":"08123456"}

Input Schema

Name	Required	Description
`staff`	No	How many people work for the company.
`regions`	No	Where the company works, e.g. ["North West", "Yorkshire and the Humber"] or ["Ontario", "Quebec"].
`summary`	No	What the company does, who for and where, in a few sentences. Leave it out to keep the description Winquill has, such as when only adding codes or a trading name; a new one replaces it.
`website`	No	The company's website, e.g. "northbridge.co.uk".
`add_codes`	No	CPV codes to add to the ones the company works under, 8 digits each, e.g. ["60130000"] when the user adds SEND transport. Pick the most specific codes that fit the work the user names; adding never takes codes off.
`workspace`	No	The Winquill workspace to use, by name, when the user is in more than one, e.g. "Northbridge Services".
`nationwide`	No	True when the company works anywhere in its country.
`buyer_types`	No	Kinds of public buyer the company has worked for, e.g. ["local_authority", "education"].
`company_name`	No	The company's name, e.g. "Northbridge Services Ltd".
`remove_codes`	No	CPV codes to take off, e.g. ["80500000"].
`trading_name`	No	The name the company bids under, when it isn't its registered name, e.g. "Plenda" for Eshmere Ltd.
`turnover_gbp`	No	Annual turnover in the company's home currency (pounds for a UK company, Canadian dollars for a Canadian one), e.g. 2400000.
`business_size`	No	The company's size, e.g. "small" for under 50 staff. Use "vcse" for charities and social enterprises.
`certifications`	No	Certifications and accreditations it holds, e.g. ["iso_9001", "cyber_essentials", "chas"]. Add an expiry as "cyber_essentials:2026-11-30".
`company_number`	No	The Companies House number, e.g. "08123456" or "SC123456", or for a US company its SAM.gov Unique Entity ID (UEI), e.g. "JX4M7Q2LK9C1". Winquill looks the company up and finds the public contracts it has won.
`largest_contract_gbp`	No	The largest contract, a year, the company would take on, in its home currency.
`public_liability_gbp`	No	Public liability (in Canada, commercial general liability) cover in the company's home currency, e.g. 5000000.
`employers_liability_gbp`	No	Employer's liability cover in the company's home currency, e.g. 10000000.
`professional_indemnity_gbp`	No	Professional indemnity cover in the company's home currency.

Output Schema

Name	Required	Description	Default
`saved`	No
`summary`	Yes
`workspace`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026

changedInput schema / properties / company_number / description

Previous value: -"The Companies House number, e.g. \"08123456\" or \"SC123456\", or for a US company its SAM.gov Unique Entity ID (UEI), e.g. \"JX4M7Q2LK9C1\". Tenda looks the company up and finds the public contracts it has won."New value: +"The Companies House number, e.g. \"08123456\" or \"SC123456\", or for a US company its SAM.gov Unique Entity ID (UEI), e.g. \"JX4M7Q2LK9C1\". Winquill looks the company up and finds the public contracts it has won."

changedInput schema / properties / summary / description

Previous value: -"What the company does, who for and where, in a few sentences. Leave it out to keep the description Tenda has, such as when only adding codes or a trading name; a new one replaces it."New value: +"What the company does, who for and where, in a few sentences. Leave it out to keep the description Winquill has, such as when only adding codes or a trading name; a new one replaces it."

changedInput schema / properties / workspace / description

Previous value: -"The Tenda workspace to use, by name, when the user is in more than one, e.g. \"Northbridge Services\"."New value: +"The Winquill workspace to use, by name, when the user is in more than one, e.g. \"Northbridge Services\"."

Changed5 schema fields changedOct 24, 2026

addedInput schema / properties / add_codes

Added value: +{
+  "description": "CPV codes to add to the ones the company works under, 8 digits each, e.g. [\"60130000\"] when the user adds SEND transport. Pick the most specific codes that fit the work the user names; adding never takes codes off.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / remove_codes

Added value: +{
+  "description": "CPV codes to take off, e.g. [\"80500000\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / summary / description

Previous value: -"What the company does, who for and where, in a few sentences, e.g. \"Commercial and school cleaning across Greater Manchester, 40 staff, mostly council and academy trust contracts.\""New value: +"What the company does, who for and where, in a few sentences. Leave it out to keep the description Tenda has, such as when only adding codes or a trading name; a new one replaces it."

addedInput schema / properties / trading_name

Added value: +{
+  "description": "The name the company bids under, when it isn't its registered name, e.g. \"Plenda\" for Eshmere Ltd.",
+  "maxLength": 160,
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "summary"
-]
```

First observedOct 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false), destructiveHint=true, idempotentHint=true, openWorld=true; the description adds content the annotations cannot: data is written to the user's team workspace, enrichment from Companies House / SAM.gov and won contracts, and an account prerequisite. It does not spell out that existing summary/codes are replaced rather than appended in some cases (the schema does, and it implies confirm-before-write mitigates loss), so it stops short of full transparency on overwrite semantics.

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 the trigger and purpose, then constraints, then exclusions, then an example — a sensible order with no filler. It is a single dense paragraph of ~6 clauses, slightly heavier than needed, but every sentence carries either a rule or a behavioral fact.

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 19-parameter mutation with 100% schema coverage and an output schema, the description supplies exactly what structured fields cannot: the trigger, the confirmation workflow, the account prerequisite, the enrichment behavior, and the scope exclusion. Nothing needed to call it safely is missing.

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?

Schema description coverage is 100%, so the baseline is 3; the description adds a cross-cutting population policy ('only company facts the user has told you... leaving out anything unsure and any personal details') plus a worked example object showing which keys a typical call contains. It does not explain individual fields (e.g. the home-currency convention on *_gbp), but the schema already does.

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+resource ('save company profile') and immediately explains the downstream purpose: 'so Winquill can remember their business for searches, fit and readiness checks and drafting'. It also names what it is not ('Not for personal profiles or CVs') and names the enrichment sources, so an agent can distinguish it from find_company or check_bid_readiness.

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 an explicit trigger ('when the user wants Winquill to remember their business'), a data-collection rule ('fill in only company facts the user has told you, leaving out anything unsure and any personal details'), a confirmation step, and a hard exclusion ('Not for personal profiles or CVs'). Requirements are stated ('Needs a Winquill account'), which is the when-not condition.

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

All Winquill tools Inspect

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

Need Help?