BinaSmart MCP Server

A company and its vacancies

get_employer

Read-only

Fetch company profile by slug, including what it does, address, location, and all job vacancies posted. Slugs come from job listings or job detail results.

Instructions

A company listed on BinaSmart: what it does, its address and location when we hold them, and every vacancy it has posted. By employer slug from list_jobs or get_job.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Employer slug, e.g. from list_jobs employer_url

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`employer`	No	Employer
`vacancies`	No	Its vacancies on BinaSmart
`source_url`	No	bina.et page this result comes from; cite it

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "employer": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "address": {
+              "description": "Address",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "city": {
+              "description": "City",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name": {
+              "description": "Name",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "sector": {
+              "description": "Sector",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "url": {
+              "description": "Employer page",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Employer"
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "vacancies": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Its vacancies on BinaSmart"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

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 and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail: address and location are returned only 'when we hold them', i.e. those fields may be absent. It says nothing about pagination or vacancy list size, which is a plausible concern for a company with many postings.

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?

Two short sentences, no filler, and the resource contents are front-loaded ahead of the input-provenance note. Slightly dense phrasing ('what it does, its address and location when we hold them') but nothing wasted.

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?

With an output schema present, the description is not obliged to explain return values, and annotations carry the read-only profile. It adequately covers scope and input sourcing; only vacancy-list volume/pagination behavior is left unaddressed.

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 coverage is 100% for the single slug parameter, which already documents the expected format ('e.g. from list_jobs employer_url'). The description reinforces provenance and adds a second valid source (get_job), a marginal gain over the schema, so the baseline 3 applies.

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 names a specific resource (a company on BinaSmart) and enumerates the payload: profile, address/location, and all posted vacancies. This clearly separates it from get_job, which returns a single posting, though it never states the verb and relies on the name to convey retrieval.

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 tells the agent where the required slug comes from (list_jobs or get_job), which implicitly routes the workflow: enumerate jobs first, then hydrate the employer. It stops short of an explicit 'use this instead of X when Y' statement or any exclusions.

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