Skip to main content
Glama
Sign In

Remotive

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Company

get_company
Read-onlyIdempotent

Company profile + active listings by company slug.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRemotive company slug

Output Schema

NameRequiredDescriptionDefault
jobsNoActive job listings from this company
companyNoCompany profile information

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "slug": "github"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "company": {
+      "description": "Company profile information",
+      "properties": {
+        "logo": {
+          "description": "Company logo URL",
+          "type": "string"
+        },
+        "name": {
+          "description": "Company name",
+          "type": "string"
+        },
+        "slug": {
+          "description": "Company slug",
+          "type": "string"
+        },
+        "website": {
+          "description": "Company website URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "jobs": {
+      "description": "Active job listings from this company",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Job category slug",
+            "type": "string"
+          },
+          "id": {
+            "description": "Job ID",
+            "type": "number"
+          },
+          "publication_date": {
+            "description": "Publication date ISO format",
+            "type": "string"
+          },
+          "title": {
+            "description": "Job title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Job listing URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds only that it returns profile and active listings, which is data scope rather than behavioral traits. No rate limits, pagination, or other behavioral details are mentioned, but with strong annotations, the lack of contradiction and some added context is acceptable.

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?

The description is a single, front-loaded sentence: 'Company profile + active listings by company slug.' It contains no superfluous words and is appropriately sized for the tool's simplicity.

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 a single required parameter, an output schema, and rich annotations (read-only, idempotent, non-destructive), the description is sufficient. It clearly states what the tool returns, and the output schema covers return-value details. Nothing critical is missing for this low-complexity tool.

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?

The schema already provides 100% coverage with the description 'Remotive company slug' for the required `slug` parameter. The tool description reinforces that the slug identifies the company and that output includes listings, but it does not add beyond the schema's semantic detail. Baseline of 3 is appropriate.

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?

The description clearly states the tool returns a company profile and active listings for a given company slug. This specific verb-less phrasing is unambiguous and distinguishes it from siblings like entity_profile by describing the exact data scope.

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 description implies use when you have a company slug and need profile plus listings, but it does not explicitly mention when to prefer this over alternatives like entity_profile or search. There are no usage exclusions or alternative comparisons.

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

All Remotive 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