stepsecurity-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_my_tenant

Retrieve your StepSecurity customer/tenant identifier and admin console link. Use this to confirm your current scope before a detection sweep or when asked 'What's my tenant?'.

Instructions

Return the StepSecurity customer/tenant identifier configured on this MCP server, along with a link to the tenant's admin console. Call this when the user asks 'what's my tenant?', 'which customer am I scoped to?', or wants to confirm the default before a detection sweep. Reads the STEP_SECURITY_CUSTOMER env var set in the MCP client config.

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": "get_my_tenant"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Apr 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, but description adequately discloses it reads STEP_SECURITY_CUSTOMER env var, is read-only, and non-destructive. Could mention error cases like missing env var, but sufficient for a simple config query.

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?

Three sentences, each adding value, front-loaded with action. No redundancy or irrelevant details.

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?

No output schema, but purpose is simple. Description covers purpose, usage trigger, and data source. Minor omission: no mention of error handling for missing env var, but overall complete.

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?

No parameters, so baseline is 4. Description adds value by explaining return value and configuration source.

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 the tenant identifier and admin console link. The verb 'Return' and resource 'tenant identifier' are specific. Among siblings like 'describe_capabilities', no overlap exists.

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?

Explicitly states when to call (user queries about tenant) and mentions it reads an environment variable. Does not specify when not to use alternatives, but context is clear.

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