Skip to main content
Glama

JustIdea Agency

by agency.justidea
OverviewDiscussionsAdmin

Send an inquiry to JustIdea

send_inquiry

Send a sales inquiry to JustIdea Agency (Kraków, Poland) on behalf of the user. It goes to the agency CRM and the sales team, the sender gets a short confirmation e-mail, and a person replies within one business day. Use only details the user gave you. Never invent a name, e-mail or phone number. Before sending, show the user what will be sent and ask for consent to data processing under the privacy policy (https://justidea.agency/en/privacy-policy/); set zgoda to true only after they agree. Budgets are in PLN net ("tys. zł" = thousand PLN). At most 2 inquiries per e-mail address per day. Urgent matters: phone +48 12 400 40 40.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imieYesFull name of the person sending the inquiry.
emailYesEmail address for the reply.
firmaNoCompany name, optional.
zgodaYesMust be true: the user agreed to the processing of the data in this inquiry under the privacy policy.
budzetYesBudget range, exactly one of the listed values, and it must match the service. One-off projects ("sklep", "strona", "audyt", "kreacja", "inne") take a project budget: "do 15 tys. zł", "15-40 tys. zł", "40-80 tys. zł", "80-150 tys. zł", "150-300 tys. zł", "powyżej 300 tys. zł", "jeszcze nie wiem". Monthly services ("seo", "wizytowka", "kampanie", "marketing", "content", "opieka") take a monthly budget: "do 2 tys. zł", "2-6 tys. zł", "6-15 tys. zł", "15-40 tys. zł", "40-100 tys. zł", "powyżej 100 tys. zł", "jeszcze nie wiem". If the user does not know the budget, use "jeszcze nie wiem" instead of guessing.
stronaNoCurrent website or online store address, optional.
uslugaYesWhat the inquiry is about: "sklep" = Sklep internetowy; "strona" = Strona internetowa; "seo" = Pozycjonowanie SEO; "wizytowka" = Wizytówka Google i Bing; "kampanie" = Kampanie reklamowe; "marketing" = Marketing, pełny zakres; "content" = Content marketing i treści; "opieka" = Opieka i rozwój serwisu; "audyt" = Audyt; "kreacja" = Identyfikacja i kreacja; "inne" = Coś innego.
telefonYesPhone number with at least 9 digits, country code welcome.
wiadomoscYesThe request in the user's own language, at least two sentences: what they need, scope, deadline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / budzet / description
      Previous value: -"Budget range, exactly one of the listed values, and it must match the service. One-off projects (\"sklep\", \"strona\", \"audyt\", \"kreacja\", \"inne\") take a project budget: \"do 15 tys. zł\", \"15-40 tys. zł\", \"40-80 tys. zł\", \"80-150 tys. zł\", \"150-300 tys. zł\", \"powyżej 300 tys. zł\", \"jeszcze nie wiem\". Monthly services (\"seo\", \"kampanie\", \"marketing\", \"content\", \"opieka\") take a monthly budget: \"do 2 tys. zł\", \"2-6 tys. zł\", \"6-15 tys. zł\", \"15-40 tys. zł\", \"40-100 tys. zł\", \"powyżej 100 tys. zł\", \"jeszcze nie wiem\". If the user does not know the budget, use \"jeszcze nie wiem\" instead of guessing."New value: +"Budget range, exactly one of the listed values, and it must match the service. One-off projects (\"sklep\", \"strona\", \"audyt\", \"kreacja\", \"inne\") take a project budget: \"do 15 tys. zł\", \"15-40 tys. zł\", \"40-80 tys. zł\", \"80-150 tys. zł\", \"150-300 tys. zł\", \"powyżej 300 tys. zł\", \"jeszcze nie wiem\". Monthly services (\"seo\", \"wizytowka\", \"kampanie\", \"marketing\", \"content\", \"opieka\") take a monthly budget: \"do 2 tys. zł\", \"2-6 tys. zł\", \"6-15 tys. zł\", \"15-40 tys. zł\", \"40-100 tys. zł\", \"powyżej 100 tys. zł\", \"jeszcze nie wiem\". If the user does not know the budget, use \"jeszcze nie wiem\" instead of guessing."
    • changedInput schema / properties / usluga / description
      Previous value: -"What the inquiry is about: \"sklep\" = Sklep internetowy; \"strona\" = Strona internetowa; \"seo\" = Pozycjonowanie SEO; \"kampanie\" = Kampanie reklamowe; \"marketing\" = Marketing, pełny zakres; \"content\" = Content marketing i treści; \"opieka\" = Opieka i rozwój serwisu; \"audyt\" = Audyt; \"kreacja\" = Identyfikacja i kreacja; \"inne\" = Coś innego."New value: +"What the inquiry is about: \"sklep\" = Sklep internetowy; \"strona\" = Strona internetowa; \"seo\" = Pozycjonowanie SEO; \"wizytowka\" = Wizytówka Google i Bing; \"kampanie\" = Kampanie reklamowe; \"marketing\" = Marketing, pełny zakres; \"content\" = Content marketing i treści; \"opieka\" = Opieka i rozwój serwisu; \"audyt\" = Audyt; \"kreacja\" = Identyfikacja i kreacja; \"inne\" = Coś innego."
    • changedInput schema / properties / usluga / enum
      Previous value: -[
-  "sklep",
-  "strona",
-  "seo",
-  "kampanie",
-  "marketing",
-  "content",
-  "opieka",
-  "audyt",
-  "kreacja",
-  "inne"
-]New value: +[
+  "sklep",
+  "strona",
+  "seo",
+  "wizytowka",
+  "kampanie",
+  "marketing",
+  "content",
+  "opieka",
+  "audyt",
+  "kreacja",
+  "inne"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false), and the description goes well beyond: it discloses where the inquiry lands (agency CRM and sales team), that the sender receives a confirmation e-mail, a one-business-day reply SLA, a rate limit of 2 inquiries per e-mail per day, and the consent/privacy-policy requirement. Rich behavioral context.

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?

Dense but front-loaded: purpose and delivery mechanics first, then constraints, then consent and budget notes. Every sentence carries operational value, though the volume of guidance makes it longer than strictly minimal.

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?

For a 9-parameter, 7-required mutation with no output schema and openWorld semantics, the description supplies everything an agent needs: consent sequencing, data-honesty rules, budget units, rate limit, alternative contact channel, and expected outcome (confirmation e-mail + reply within one business day).

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?

Schema coverage is 100%, so baseline is 3. The description adds real value beyond the schema: budgets are PLN net with 'tys. zł' = thousand PLN, and zgoda must be set true only after the user agrees to data processing. These clarify units and the consent gate's intent.

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?

States a specific verb and resource ('Send a sales inquiry to JustIdea Agency') with clear scope. This is instantly distinguishable from all siblings (get_page, scan_*, list_services, search_site), which are read/scan operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use only details the user gave, never invent contact data, show the user what will be sent and obtain consent before sending, and route urgent matters to phone +48 12 400 40 40. Concrete when-to-use conditions and constraints are all present.

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

All JustIdea Agency 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