savi-tools

Business profile

get_business_profile

Read-only

The business’s own profile: legal name, entity type, the tax return it files, accounting method, fiscal year, industry, and address. Answers "what tax form does my business file and what is my fiscal year?"

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ein`	Yes
`address`	Yes
`orgMode`	Yes
`industry`	Yes
`ownerName`	Yes
`entityType`	Yes
`taxElection`	Yes
`businessName`	Yes
`fiscalYearEnd`	Yes
`taxReturnForm`	Yes
`accountingMethod`	Yes
`taxReturnFormLabel`	Yes
`expenseBillingPolicy`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accountingMethod": {
+      "type": "string"
+    },
+    "address": {
+      "properties": {
+        "city": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "state": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "street": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "zip": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "street",
+        "city",
+        "state",
+        "zip"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "businessName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ein": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "entityType": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "expenseBillingPolicy": {
+      "type": "string"
+    },
+    "fiscalYearEnd": {
+      "type": "string"
+    },
+    "industry": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "orgMode": {
+      "type": "string"
+    },
+    "ownerName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "taxElection": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "taxReturnForm": {
+      "type": "string"
+    },
+    "taxReturnFormLabel": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "businessName",
+    "ownerName",
+    "entityType",
+    "taxElection",
+    "taxReturnForm",
+    "taxReturnFormLabel",
+    "accountingMethod",
+    "expenseBillingPolicy",
+    "fiscalYearEnd",
+    "orgMode",
+    "industry",
+    "ein",
+    "address"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds value by listing specific fields and the question answered, beyond what annotations provide. No contradiction.

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?

Two sentences, no filler, front-loaded with key purpose and field list. Extremely efficient.

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?

Given the output schema exists, the description covers all needed context: what data is returned and why it's used. Perfect for a simple read-only tool.

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 exist, so description doesn't need to add param info. Baseline 4 for zero-parameter tools 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 retrieves the business's own profile with specific fields like legal name, entity type, tax return, etc. It answers a concrete question, distinguishing it from sibling tools like get_client_summary.

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?

The description implicitly conveys usage context by specifying it's the business's own profile, and no alternative for this purpose exists among siblings. However, it lacks explicit when-not or alternative guidance.

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

All savi-tools tools Inspect

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

Need Help?