Skip to main content
Glama

JobSheet MCP Server and API by Cotlet

Import company from Companies House in JobSheet

jobsheet_import_company_from_companies_house
Read-onlyIdempotent

Import company from Companies House in the user's own JobSheet account from ChatGPT, Claude or any AI agent. Returns how to do it in JobSheet step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's JobSheet Cloud Browser. JobSheet's official API: JobSheet publishes no public API, webhooks or Zapier app; it connects only to Xero, as a paid add-on, and Companies House (checked 8 Nov 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jobsheet_import_company_from_companies_house"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the tool opens nothing by itself and only returns instructions with screens, buttons, and fields. It also adds important integration context: JobSheet has no public API, webhooks, or Zapier app, and connects only to Xero as a paid add-on and Companies House.

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?

The description is compact and conveys the key handoff to browser tools, but the opening sentence repeats the title before clarifying the actual guide-only behavior. There is minor redundancy in the API sentence, though the constraints are relevant.

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?

With no output schema, the description explains what is returned: step-by-step guidance covering screens, buttons, and fields. It also makes clear that the tool itself does not execute the import and that browser tools must be used afterward.

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?

There are zero parameters, so the schema baseline applies and no additional parameter meaning is needed. The description correctly does not invent parameter details.

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?

The description ultimately states that this tool returns step-by-step instructions for importing a company into JobSheet, rather than performing the import itself. It distinguishes the tool from the cotlet_browser_* execution siblings, though the opening 'Import company' phrasing is initially misleading.

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?

It clearly says to use this tool to get the steps and then use cotlet_browser_* tools to perform the action in the user's Cloud Browser. It does not explicitly compare against cotlet_app_guide or state when not to use this tool, so it stops short of full alternative guidance.

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