Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Identity Providers for Company

machship_get_identity_providers_for_company
Read-onlyIdempotent

Retrieve all identity providers linked to a company by company ID, enabling configuration checks and access management for Machship integrations.

Instructions

Get all identity providers associated with a specific company.

Args:

  • companyId (number): Company ID

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": {
      "companyId": "<companyId>"
    },
    "name": "machship_get_identity_providers_for_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesCompany ID

Output Schema

NameRequiredDescriptionDefault
errorsNoValidation errors returned by Machship, if any
objectNoResponse payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / companyId / maximum
      Added value: +9007199254740991
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "errors": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Validation errors returned by Machship, if any"
+    },
+    "object": {
+      "description": "Response payload from the Machship API"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds only the word 'all', hinting results are unpaginated/complete, and says nothing about permission requirements to read another company's providers or about failure when the company is unknown. That is modest added context against a low bar.

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 purpose sentence is front-loaded, short, and waste-free. The trailing Args block duplicates the schema and could be dropped without loss, which keeps it from a 5.

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?

This is a simple single-parameter read tool with full annotation coverage, 100% schema description coverage, and an output schema that documents the return value. The description states what is fetched and for which entity, so nothing essential is missing — the only gap, sibling disambiguation, is a scoring issue under purpose clarity rather than a completeness failure.

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?

Schema description coverage is 100% and the single companyId parameter is fully documented in the schema with type and bounds. The description merely restates 'companyId (number): Company ID' in an Args block, adding no meaning such as where to obtain the ID or whether other identifiers are accepted; baseline 3 applies when the schema does the work.

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 states a specific verb and resource ('Get all identity providers') and scopes it to 'a specific company', so the purpose is unambiguous. However, it never distinguishes itself from the closely named siblings machship_get_identity_providers_for_organisation, machship_get_identity_providers_for_logged_user, or machship_get_identity_provider, leaving an agent to infer the difference from names alone.

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?

Usage is only implied by the 'associated with a specific company' scoping — an agent can guess this is the tool for company-scoped lookups rather than organisation- or logged-user-scoped ones. There is no explicit when-to-use statement, no exclusion of the sibling variants, and no note on when a companyId would be unavailable.

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

Deploy Server

Other Tools